feat: add conformance scenario for SEP-2164 resource-not-found error code#200
Open
feat: add conformance scenario for SEP-2164 resource-not-found error code#200
Conversation
…code Adds a draft-scoped scenario verifying servers return -32602 (Invalid Params) for non-existent resources instead of the legacy -32002 or an empty contents array. Includes a sep-2164.yaml traceability file mapping each MUST/MUST NOT/SHOULD to its check per the proposed SEP-2484 process.
commit: |
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
1 participant
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.
Adds a conformance scenario for SEP-2164, which standardizes the resource-not-found error code from
-32002to-32602(Invalid Params).What's tested
The scenario
sep-2164-resource-not-foundattempts to read a URI the server does not recognize and verifies the error response:sep-2164-error-code-32602(not-32002, not empty contents)sep-2164-data-uridataincludes the requesteduriThe scenario is scoped to
specVersions: ['draft']only — it does not run against dated spec versions until SEP-2164 is incorporated into a release.Traceability
Includes
src/scenarios/server/sep-2164.yamlmapping each normative requirement to its check, following the format proposed in SEP-2484.Verification
-32602;data.uriyields WARNING since the SDK doesn't populate it yet)-32002explicitly references SEP-2164 to guide SDK maintainers during migration-32002,-32603, empty contents, and non-JSON-RPC errors