Repository navigation
Conversation
The learn/client-concepts elicitation/create example used 'schema', but the specification and JSON schema define the field as 'requestedSchema'. Signed-off-by: FenjuFu <[email protected]>
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.
What
Fixes the elicitation request example in
docs/docs/learn/client-concepts.mdx.The example used a
schemafield:but the canonical field name is
requestedSchema. This matches:schema/draft/schema.ts/schema/2025-06-18/schema.ts(ElicitRequest.params.requestedSchema)schema/draft/examples/ElicitRequest/elicitation-request.jsondocs/specification/2025-06-18/client/elicitation.mdxWhy
A reader copying the learn-page example would send
params.schema, which aspec-compliant client ignores (it reads
params.requestedSchema), so theelicitation form would be empty. The fix aligns the learn doc with the spec.
Change
One-line field rename
schema:→requestedSchema:in the elicitationcomponents example. No other content changed.