Object keys uniqueness check #461
Merged
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
johakoch
force-pushed
the
object-keys-uniqueness-check
branch
from
842ce3e
to
4a957d3
Compare
afflerbach
reviewed
Apr 4, 2022
Co-authored-by: Joe Afflerbach <joe.afflerbach@avenga.com>
afflerbach
approved these changes
Apr 4, 2022
This was referenced Apr 4, 2022
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.
Keys in an object type attribute value are only handled case-insenstively if reasonable (e.g. the represent HTTP methods or header field values).
Reviewer checklist