v2.3.0

Fixs

• Collections issue with pristine : remove items did not break form's pristine because of removed items could not influence it, now collection have its own pristine state

What does it change?

• Triggering a collection's method will update the pristine state of the collection, as well as the form's pristine state (in addition to updating the mounted fields managed by this method trigger). You can disable these updates by passing the keepPristine option to the method as true.
• The collection's methods setKeys, remove, and removeMultiple now accept a second parameter options object with the keepPristine property.

v2.2.3

Fixs

• useForm internal state was not update when it changed
• collections were never remove from form collection, even if the useCollection was unmount

v2.2.2

Fixs

• Replace uniqid dependency by short-unique-id (#215)

v2.2.1

Fixs

• useCollection:
  • performances issues caused by useless re-renders
  • setKeys not shared collection method

v2.2.0

Features

• stateSubscription on useForm and useFormContext

Fixs

• reset options type
• useCollection methods options missing in type

v2.1.0

• [FIX] Initial resetKey that was automatically set to 1
• Reset form with updated config on useForm id change

Formiz v2 🎉

This v2 is focusing on performances, React 18 and internal code simplification for better contributions.

See our Migration Guide

v1.8.1

• fix: Upgrade lodash-es
• fix: Issue with array syntax with setFieldsValues and keepUnmounted option

v1.8.0

What's Changed

Major stability upgrade 🤩 (Fix issue #100 and #82)

• No more layout shift when using steps
• No more out of sync data when using setFieldsValues or invalidateFields synchronously

Full Changelog: v1.7.1...v1.8.0

v1.7.1

What's Changed

• fix(core): Prevent issue with validating.end() called synchronously by @ivan-dalmet in #99

Full Changelog: v1.7.0...v1.7.1