kusiewicz
kusiewicz
FYI guys the same problem occurs when I'm using `@tanstack/react-forms`. I get the same error, and stack trace points to tanstack-forms.
@SutuSebastian > 2. If we update the packages we get the following error: https://github.com/TanStack/router/issues/4409
I think related to: https://github.com/TanStack/form/pull/1706
The `formOptions` function is a simple helper designed for creating reusable configurations. A practical example is when you want to split a large form across multiple files. In that scenario,...
I updated to the latest version and still has not typed values in validators. So how it should look like?
@LeCarbonator Ok, It makes sense. However, from what I can see in the documentation, there is not even a word about `onServer`. Can you elaborate on this poorly typed SSR...
> @kusiewicz can you fix merge conflicts and then @LeCarbonator if you could, re review for @kusiewicz since the blocker is merged? > > Thanks! Will do today!
https://react.dev/learn/rendering-lists#why-does-react-need-keys :)
Actually the behavior you're seeing is correct based on how you've configured the form. You've defined a _form-level_ `onMount`, but you're expecting _field-level_ `onMount` behavior. I've forked [your sandbox](https://stackblitz.com/edit/vitejs-vite-rzlvmqw6?file=src%2FApp.tsx)
Actually I've just run into a similar problem. So you're logging out `onMount` `form` errors - they actually exist immediately - before `Show` btn is clicked. But its not synced...