fix: propagate notification params #98
Merged
Conversation
This file contains 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
jerome3o-anthropic
deleted the
jerome/fix/propagate-notification-params
branch
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.
Model Context Protocol SDK: Pass through progress params
Motivation and Context
Support additional fields in progress notifications beyond just
progressandtotalby passing through all notification parameters to handlers.How Has This Been Tested?
Verified through existing protocol tests and usage scenarios requiring extended progress information.
Breaking Changes
None. Maintains backward compatibility while enabling additional progress parameters.
Types of changes
Checklist
Additional context
Modified
_onprogressto only extractprogressTokenand pass remaining params through to handlers. Version bump 1.0.3 → 1.0.4.