fix: register logging/setLevel handler via registerCapabilities #1508
+60
−10
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
registerCapabilitiesto properly register thelogging/setLevelrequest handler when the logging capability is added after constructionregisterLoggingHandler()method with an idempotency guard, called from both the constructor andregisterCapabilities()setLoggingLevelworks when logging is registered viaregisterCapabilities()Fixes #1464
Test plan
client.setLoggingLevel()works when server usesregisterCapabilities({ logging: {} })instead of constructor optionsregisterCapabilities()🤖 Generated with Claude Code