Align list order validation and query error fields - #36
Merged
Merged
Conversation
SaladDay
marked this pull request as ready for review
September 22, 2026 17:05
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.
Explicit empty list order previously followed the descending default. Reject supplied values outside
asc/desc, preserve omission, and emit the measured Beta, Files and Skills error fields through the existing parser and error serializer. Align invalid Vault/Credential status errors without changing limits, cursor lookup, tenancy or execution.Nine-family acceptance uses fixed SDK 3.13.0 and raw HTTP against actual Core/PostgreSQL. The SDK drops empty query strings, so raw HTTP exercises
order=; SDK calls verify omission and nonempty invalid values. Preserve successful pagination and history, authentication, tenant isolation and unchanged resource snapshots. Files verbose messages/detail and other query differences remain explicitly recorded.Validation: targeted API/contract tests and real service acceptance passed;
make openapiand diff checks passed. Servermake -o check-web checkpassed ate4cb8a5, including actual PostgreSQL acceptance and generated-query checks. Fresh independent Astra high review found no grounded in-scope findings; API tests and diff check passed independently. Web/client source and dependencies are unchanged from PR #35; reuse that exact-source Web qualification (287 client tests, 583 Web tests, 76 browser cases) rather than claiming a new UI run. The optional packaged MiniMax native-tools probe was skipped. No model/provider/Runtime changes or new native capability qualification.