Releases: form-atoms/field
v4.0.3
v4.0.2
v4.0.2-next.2
v4.0.2-next.1
4.0.2-next.1 (2024-01-14)
Bug Fixes
v4.0.1
v4.0.0
4.0.0 (2024-01-05)
BREAKING CHANGES
- the ListField no longer uses path access to form fields, instead it works directly with the new
listField() - The EmptyMessage render prop has been renamed to simply Empty:
<ListField
field={fields.luckyNumbers}
- EmptyMessage={() => <p>No lucky numbers</p>}
+ Empty={() => <p>No lucky numbers</p>}
>- fix(ListField): Rename render props for add/remove button
BREAKING CHANGE
the AddItemButton and RemoveItemButton props were renamed to AddButton and RemoveButton respectively.
-
docs(ListField): fix nested example
-
fix(listAtom): reset nested forms
-
fix(listField): adding new item to list revalidates field with a change event
-
fix(listField): revalidate the field with change event when the item is removed
-
test & callback wrapper
-
fix: nested listAtom in listAtom validation
v4.0.0-next.1
4.0.0-next.1 (2024-01-05)
BREAKING CHANGES
- the ListField no longer uses path access to form fields, instead it works directly with the new
listField() - The EmptyMessage render prop has been renamed to simply Empty:
<ListField
field={fields.luckyNumbers}
- EmptyMessage={() => <p>No lucky numbers</p>}
+ Empty={() => <p>No lucky numbers</p>}
>- fix(ListField): Rename render props for add/remove button
BREAKING CHANGE
the AddItemButton and RemoveItemButton props were renamed to AddButton and RemoveButton respectively.
-
docs(ListField): fix nested example
-
fix(listAtom): reset nested forms
-
fix(listField): adding new item to list revalidates field with a change event
-
fix(listField): revalidate the field with change event when the item is removed
-
test & callback wrapper
-
fix: nested listAtom in listAtom validation