fix: nullable json-rpc id instead of optional#1281
+3 −3
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.
Deny undefined for json-rpc error response id, make it spec compliant.
https://www.jsonrpc.org/specification#response_object
Fix for the change in: #1242.
Related: modelcontextprotocol/modelcontextprotocol#1939
How Has This Been Tested?
unit tests, type checking
Breaking Changes
undefined won't be allowed as id
Types of changes
Checklist