Repository navigation
Conversation
JSON-RPC 2.0 section 5.1 assigns -32602 to invalid method parameters. Map typed request decoding failures to that code before invoking the registered handler.
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.
When a request's parameters cannot be decoded for its method, the SDK returns JSON-RPC error
-32602with the original request ID. Previously, the decoding error reached the generic internal-error handler and returned-32603.The regression tests send two malformed
tools/callrequests over an in-memory connection, one missing the tool name and one supplying an array forarguments. The change applies to typed request dispatch on all supported platforms and does not change public Swift API signatures. JSON-RPC 2.0 §5.1AI assistance: Codex drafted the code, tests, and PR description.