Fix inconsitency between general processing rules and pagination links #1606
Conversation
This file contains hidden or 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
`null` value was not listed as an allowed value for links in general processing rules for links objects. But it was allowed explicitly for pagination links. This change fixes that inconsitency by allowing `null` for _every_ link to indicate that it does not exist.
9 tasks
jelhan
commented
Feb 23, 2022
auvipy
reviewed
Feb 24, 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.
nullvalue was not listed as an allowed value for links in general processing rules for links objects. But it was allowed explicitly for pagination links. This change fixes that inconsitency by allowingnullfor every link to indicate that it does not exist.Closes #887