feat(fetch): add safeParse function #2
+118
−7
Conversation
This file contains 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
|
lgtm 🙏 |
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.
Almost all supported type parsers (
zod,valibot,valita) have two options for validating: throwing errors and returning a Result union object. Currently@fuman/fetchonly provides the former option, which is harder to use if you want to implement custom error handling or stick to explicit flow control.This PR addresses this issue and adds
safeParsefunction toFfetchTypeProviderthat uses the Result-based validating.yupsadly doesn't have a way to execute validation without throwing, so a simple try-catch wrapper was implemented.