Hi, my name’s Aaron Powell and I’m a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
To integrate with formik (and just to be transparent, I'm not an expert on formik) I would start with wrapping the <form> element with <Formik> and provide it with the information for current page (the fields and values), but not the whole form.
This way formik doesn't have to concern itself with the fact that it's a multi-step form or that there's conditional logic, you're handling that externally, and formik looks at the current form view.
Id really love to create a template for dynamic forms and use it everywhere in the app. The issue is in the layout the UX team provides. It is often times very different on each page so it might be hard to include props for layout as well. Stripping the code from conditional logic and steps might work. I will probably try it out this year.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great post on dynamic forms. Im curious how this would play with formik forms and yup validation.
To integrate with formik (and just to be transparent, I'm not an expert on formik) I would start with wrapping the
<form>element with<Formik>and provide it with the information for current page (the fields and values), but not the whole form.This way formik doesn't have to concern itself with the fact that it's a multi-step form or that there's conditional logic, you're handling that externally, and formik looks at the current form view.
Thanks for the input man!
Id really love to create a template for dynamic forms and use it everywhere in the app. The issue is in the layout the UX team provides. It is often times very different on each page so it might be hard to include props for layout as well. Stripping the code from conditional logic and steps might work. I will probably try it out this year.