64d22def02
* fix: don't respond to unparseable messages * docs: spell 'unparsable' to satisfy typos linter * fix: only ignore unparsable JSON, keep protocol errors visible Classify the serde error in the receive loop: syntax/EOF errors are unparsable input with no correlatable id (issue #938) and stay silent, while data errors (valid JSON that doesn't match the message shape) are real protocol errors and get an error response instead of being dropped. Add a test covering the protocol-error path. * fix: respond with Invalid Request for malformed protocol messages --------- Co-authored-by: tsouth89 <tsouth89@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| rmcp | ||
| rmcp-macros | ||