Make sure effectiveReference is not present in v1 REST API responses
#7512
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
Minor test tweak to ensure that JSON responses to v1 clients do not contain v2 attributes in the payload. Previously the test parsed JSON using current java client classes, which could mask the presence of `null` values in `effectiveReference` attributes (the parsing would succeed).
snazy
approved these changes
Sep 19, 2023
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.
Minor test tweak to ensure that JSON responses to v1 clients do not contain v2 attributes in the payload. Previously the test parsed JSON using current java client classes, which could mask the presence of
nullvalues ineffectiveReferenceattributes (the parsing would succeed).