-
Notifications
You must be signed in to change notification settings - Fork 85
feat: add pure-parse #1417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add pure-parse #1417
Conversation
# Conflicts: # package-lock.json # package.json
Of course. This project doesn't restrict you from changing anything as long as it adheres to the criterion outlined in the README. |
I meant: if it is okay to include a library that is in "beta" in these benchmarks; but it seems so 🙂 I will follow up with another pull request when v1.0.0 is released. |
Oh ya, definitely can. If it can be installed using npm, then it's good to go 😁 |
Hello, I'd like to add a new library to the benchmarks, PureParse:
It does
parseSafeparseStrictassertLooseFor validation of objects, there are two alternate parsers/guards: non-compiled and just-in-time compiled. I was not sure how to differentiate between these two in the cases, so I appended the string
(JIT compiled)to the case name.I am the author of this library.
I tried my best to make all the necessary modifications (based on previous pull requests), but please do let me know if I need to do something differently.
The current version is
0.0.0-beta.7. I don't anticipate any major changes right now, but as long as it's in beta, I reserve the rights to make breaking changes. Is that okay?