Fix serializer for CreateElicitationResult #240
Merged
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.
Motivation and Context
Fixes: #233
The issue appeared due to fallback-style
RequestResultPolymorphicSerializer
implementation:CreateElicitationResult
is aClientResult
with anaction
field https://modelcontextprotocol.io/specification/draft/client/elicitationselectClientResultDeserializer
function was missing a case for the action fieldselectServerResultDeserializer
found the content field and incorrectly mapped it toCallToolResult.serializer()
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context