Allow any Collection to be encoded as OPAQUE in NDK metadata #1728
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lemnik
force-pushed
the
PLAT-8756/ndk-metadata-collections
branch
from
419a0c4 to
70bef5f
Compare
Android notifier sizes
Generated by 🚫 Danger |
lemnik
force-pushed
the
PLAT-8756/ndk-metadata-collections
branch
2 times, most recently
from
a6da405 to
f8c4fda
Compare
…ynamically linked modules
lemnik
force-pushed
the
PLAT-8756/ndk-metadata-collections
branch
from
f8c4fda to
2557b30
Compare
nickdowell
approved these changes
Aug 9, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Allow any valid
Collectionto be encoded as OPAQUE NDK metadataTesting
Additional values in the end to end test