Open moshloop opened 2 weeks ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
flanksource-ui | ❌ Failed (Inspect) | Jul 3, 2024 9:04am |
Name | Link |
---|---|
Latest commit | 7f245e1eebd789d30dcac9c038b9c5cf6271c1dc |
Latest deploy log | https://app.netlify.com/sites/clerk-saas-ui/deploys/668513b0e81d6e0008e70bbb |
Name | Link |
---|---|
Latest commit | 7f245e1eebd789d30dcac9c038b9c5cf6271c1dc |
Latest deploy log | https://app.netlify.com/sites/goofy-euclid-75956c/deploys/668513b0fe5112000869fedd |
Name | Link |
---|---|
Latest commit | 7f245e1eebd789d30dcac9c038b9c5cf6271c1dc |
Latest deploy log | https://app.netlify.com/sites/flanksource-demo-stable/deploys/668513b0dbf8420008fdef9d |
@moshloop initialValues can only be set once in formik, before initialization, not after, when the form is loaded, you would need to update values, which you can do with the FormikContext, which you can setFieldValues, with the fields you need to update. I think we need to try and not deviate from this standard usage, which is already established, as long as the child component is inside a Formik form, it has access to the FormikContext and can be used to manipulate form values.
Goals: