Add Form about ui HOT 4 CLOSED

After taking a look around, I don't think we need to provide our own Form component.

AFAIK, the design language we're leading with in our own apps has all forms inside the sidepanel (as forms are "actionable"). In these sidebars, there's no additional styling needed to signify there's a form; placing input fields is enough. All a form provides is a state container and some validation logic for these inputs.

I'm a fan of formik, in comparison to other form helpers like react-form and formsy, because of its simplicity and familiar API. It's closely based on the native form and input components and allows you to easily plug in your own custom inputs (rather than forcing you to adhere to their own API or make vendor-specific custom inputs). Our own input components, like those in #67, will work transparently with formik.

I don't see much point in re-exporting it from this package; we can just include formik (or even another form implementation) whenever an app needs a form in its sidepanel. For other app developers, we can add a suggestion in a "tips and tricks" wiki or app tutorial later.

Thoughts @bpierre?

from ui.

Agree, <form> is behavioral and shouldn’t be provided by Aragon UI if possible.

Our own input components, like those in #67, will work transparently with formik.

formik sounds good! I never tried it, but I remember having some difficulties to make styled components work with react-formal on a project.

If formik becomes our recommended solution to manage forms, maybe we should rename our Field component to something else (e.g. FieldBlock, FieldSection)?

from ui.

If formik becomes our recommended solution to manage forms, maybe we should rename our Field component to something else (e.g. FieldBlock, FieldSection)?

Maybe LabelledField? The other two sound too "style-derived". Names are hard D:

from ui.

Closing this, as we're not providing our own form element. Renaming can happen later, if we see the need to recommend formik.

from ui.