docs: correct the response validation section - #14
Merged
Conversation
Validation no longer goes through valibot directly, so "if valibot isn't installed at runtime, validation is silently skipped" was wrong on both counts: nothing checks for valibot, and skipping is decided solely by whether the command carries a responseSchema. Describe the trigger that actually exists, and say Standard Schema rather than valibot throughout, since any spec-compliant validator works. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
If valibot isn't installed at runtime, validation is silently skippedwas wrong as of v14.0.0. Nothing checks for valibot any more — the client goes through Standard Schema's~standardinterface, and whether validation runs is decided solely by whether the command carries a staticresponseSchema.Replaces that sentence with the trigger that actually exists, and refers to Standard Schema rather than valibot throughout, since any spec-compliant validator works now.
valibotstays as the optional peer dependency and the worked example.Docs only, no code change.