fix: custom result deserialization conflic with rust_mcp_schema::Result #44
Conversation
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
hashemix
changed the title
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.
📌 Summary
The deserialize implementation for
ResultFromServerwas inconsistent withResultFromClient, leading to ping results from various MCP servers being deserialized into aCustomResultinstead of aServerResult.This issue arose because
rust_mcp_schema::Resultoverlaps withCustomResult, as both can accept arbitrary attributes.The deserialize implementation has been updated to correctly return the appropriate type. However,
CustomResultwill be deprecated in favor ofrust_mcp_schema::Resultto eliminate this conflict.