sif-formik-to-rhf

To migrate a form from Formik to React Hook Form (RHF), the process maps existing Formik patterns to RHF equivalents while preserving identical field names, validation rules, and data mapping. This ensures the form's input behavior and data flow remain unchanged during the transition.

Maintaining i18n keys during a Formik to RHF conversion involves directly preserving the existing internationalization identifiers within the new RHF component structure. The migration process ensures error handling and validation messages retain their original i18n keys and data shape.

Yes, you can migrate a single form from @navikt/sif-common-formik-ds to @sif/rhf without changing data flow. The migration targets one form at a time, ensuring that exact enum-based FormFields, useSifValidate integration, and overall data mapping are strictly preserved.

Migrating exact enum-based FormFields from Formik to RHF involves mapping the existing enum structures directly into the new React Hook Form schema. This satisfies integration requirements for RHF and useSafValidate while ensuring the field definitions and validation logic remain identical.

A key limitation of migrating Formik forms to React Hook Form is that the process is designed to be applied one single form at a time rather than migrating an entire application's schema at once. It focuses strictly on preserving existing behavior without introducing new validation logic.