Repository navigation
fix(apps): reject unsupported native API route parameters - #713
Merged
KAJdev merged 5 commits intoNov 11, 2026
Merged
Conversation
justinwlin
approved these changes
Nov 11, 2026
justinwlin
left a comment
Contributor
There was a problem hiding this comment.
Looks good. The check matches what the runtime can call, and the tests fail without the change. Two notes inline, not blocking.
KAJdev
deleted the
zeke/con-2064-validate-native-api-route-signatures-and
branch
November 11, 2026 21:39
Promptless documentation updates
|
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.
Native API routes accepted parameters that requests could not populate.
GET /search?q=worldreturned{"q": "hello"}because native handlers did not bind query parameters. Required parameters could fail with HTTP 500, and body annotations did not validate fields.Now native declarations require literal paths and instance methods with no input, or one required positional JSON-object argument for POST, PUT, PATCH, and DELETE. Unsupported signatures and schema annotations fail during application import with guidance to use a FastAPI factory.
Request-body handling is covered by the companion runtime PR #13. Both releases are needed for the complete contract.
Refs CON-2064.