feat: apply elicitation defaults client-side for SEP-1034 #1097
+205
−17
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.
Implements client-side default value application for elicitation responses as specified by SEP-1034.
Motivation and Context
SEP-1034 specifies that clients SHOULD apply default values when users omit optional fields in elicitation responses. This PR implements this behavior by overriding
setRequestHandlerto automatically apply defaults from the schema before sending responses back to the server.How Has This Been Tested?
{}, SDK fills in defaults automaticallyBreaking Changes
None.
Types of changes
Checklist
Additional context
This implements the client-side responsibility for SEP-1034 default values. The Client SDK automatically applies defaults using the configured JSON Schema validator (AJV or CfWorker) when elicitation handlers return partial/empty content.