fix(typebox): support nested extension query keys - #3697
Closed
tonycoder-hub wants to merge 1 commit into
Closed
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
tonycoder-hub
force-pushed
the
fix/typebox-query-syntax-extension-sort
branch
from
608f7a4 to
c028e7f
Compare
August 13, 2026 12:12
Copy link
Copy Markdown
Author
|
Closing as stale — opened on or before 2026-08-17 and still unmerged. |
Sorry, something went wrong.
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
1 participant
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.
Summary
querySyntax currently accepts nested extension fields for property queries, but $sort and $select only expose top-level schema keys. As a result, valid nested extension keys such as profile.name are rejected. This change derives sortable/selectable nested keys from non-operator extension entries while continuing to exclude $-prefixed query operators.
Fixes #3526.
No.
Verification
Other Information
The implementation and review used AI assistance. The final diff, regression behavior, type checks, and test results were independently verified before submission.