feat: rule now allows page[foo] defined without deepObject.#11
Merged
Conversation
apisyouwonthate-releasebot Bot
pushed a commit
that referenced
this pull request
Apr 22, 2026
## [2.2.0](v2.1.1...v2.2.0) (2026-04-22) ### Features * rule page-parameter now allows page[foo] without deepObject ([#11](#11)) ([749ead6](749ead6))
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
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.
Before it was demanding a deepObject, which not all tooling supports, and even when they do it somehow loses something.
Here is the deepObject rendered in Scalar.
I think I prefer this sort of view.
To do that (with the way existing tools work) it needs to be listed as two parameters.
So I've made the rule respect this sort of structure (without specifying exactly what page[foo] you use, as JSON:API does not either.