TanStack
add effect-form-adapter
Adapted from zod-form-adapter.
https://github.com/Effect-TS/effect/tree/main/packages/schema
☁️ Nx Cloud Report
CI is running/has finished running commands for commit c3b60b4f3fc88946fe83dc32bd4de3e7dbc73dd7. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
| 🟥 Failed Commands |
|---|
nx affected --targets=test:format,test:sherif,test:knip,test:eslint,test:lib,test:types,test:build,build --parallel=3 |
Sent with 💌 from NxCloud.
![nx-cloud[bot] avatar](https://avatars.githubusercontent.com/in/80458?v=4 "Published by a pub.dev verified publisher"){kind=small}
I love this!! Thank you so much for making such a big contribution as your first time contributing!
Let's add docs + examples, then get this one merged in!
Hey @jessekelly881 - wanted to check in on this. It's still marked as a draft PR, but otherwise LGTM. Is there anything we're waiting on prior to a review/merge?
Hey @crutchcorn! At the moment it's missing an example for angular(I haven't used angular in a very long time and I am having some issues getting the examples running on my local for some reason.. :( ), a proper solution to the typeof schema === "function" issue I mentioned (the solution I have at the moment is incorrect sense function() {} is a "constructible" in js), I want to extend the createValidator api a little bit(there are other ways to create a validator that make sense) and probably docs but I'm not yet sure where the docs need updated yet.
Sounds good! Let me know if there's anything questions I can help answer with the local setup or anything of the nature ☺️
Keep up the great work!
I'm currently running into this error with the angular examples(all of them). But the suggested solution of setting "preserveSymlinks" to true doesn't seem to work. https://github.com/angular/angular/issues/54147
Sorry all, we've ultimately decided to axe custom validators that don't support Standard Schema. It was too high of a maintenance burden for us and most of the big libraries either already do or plan to support it in the future.