Replies: 1 comment 1 reply
-
using tanstack form for the most part, but not with next-safe-action yet |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to see if there's still a use case for react-hook-form since you can now get form state from the server with the useActionState hook and next-safe-action. The only use case I'm seeing for using react-hook-form still is to handle input (field) state changes on the client side, but is react-hook-form a bit too complex just for this use case now? Seems like a more lightweight hook for form input state would be better when combined with next-safe-action and the latest next and react action state functions/hooks.
The problem I'm having with react-hook-form now is my form components are absurdly complex, especially when using shadcn/ui form components - I end up with too many abstractions that seem unnecessary now. Anybody else having this problem and how did you solve or think to solve it?
Before I refactor my form components (not looking forward to this), is there still a use case for keeping react-hook-form or is it pretty much outdated now?
Beta Was this translation helpful? Give feedback.
All reactions