fix: correct MISSING_REQUIRED_CLIENT_CAPABILITY error code to -32021 - #10
Open
MyNameIsMeerkat wants to merge 1 commit into
Open
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
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.
Updates the Missing Required Client Capability error code from
-32003to-32021to match the shipped core specification.Motivation and Context
Core renumbered this error code as part of the
2026-07-28release and corrected its own copy of SEP-2663 in commit 9b44c6b ("fix: correct MISSING_REQUIRED_CLIENT_CAPABILITY error codes in SEP-2663"). The conformance suite followed and now asserts-32021.This repository did not seem to renumber. Both
specification/draft/tasks.mdand its copy of SEP-2663 still specify-32003throughout their text.The practical effect is that the conformance suite currently tests for an error code the extension's normative text does not define. A server author who implements this specification literally will emit
-32003for a non-declaring client and fail conformance, with the spec on their side and the test suite against them.How Has This Been Tested?
NA. The change is to error code literals in normative prose + JSON examples. No schema changes. The resulting code matches what the conformance suite already asserts.
Breaking Changes
None
Types of changes
Checklist
Additional context
None