Releases: BearStudio/formiz
Releases · BearStudio/formiz
v2.4.5
Fixs
- Issue managing common types as collection item (with field name like
collection[index]
). Remove this kind of item could cause an issue of lost data - Issue with initialValues after a form reset, initialValues were kept even if the data were already reset, so on unmount/re-mount we had those values set another time.
v2.4.3
Fixs
- useCollection issue with defaultValue on reset : using a useCollection with a defaultValue but no initialValues, reset just clear the collection keys instead of put back defaultValue
- v2.4.2 introduce an issue with collection defaultValue set, just fix it
v2.4.1
FIX
- Last release break usage of
form.collection(collectionName)
, just fix it
v2.4.0
v2.3.1
Fixs
- Collection's pristine state reset: there was an issue resetting form but not these values (with
form.reset({ exclude: ["value"] })
for example), the pristine was not reset
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 astrue
. - The collection's methods
setKeys
,remove
, andremoveMultiple
now accept a second parameter options object with thekeepPristine
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
v2.2.1
Fixs
useCollection
:- performances issues caused by useless re-renders
setKeys
not shared collection method
v2.2.0
Features
stateSubscription
onuseForm
anduseFormContext
Fixs
reset
options typeuseCollection
methodsoptions
missing in type