All Versions
Latest Version
Avg Release Cycle
30 days
Latest Release
75 days ago

Changelog History
Page 1

  • v6.5.1

    July 13, 2020

    โšก๏ธ Hi, @erikras here. The primary reason for this update is to remove the Scarf dependency. I already did for Final Form and I thought React Final Form did not have its own dependency, but I was mistaken. Apologies for the delay.

    You can read about my feelings about Scarf here:

    Open Source Sustainability

    ๐Ÿ›  Deps Fixes

    • โœ‚ Remove scarf dep #831

    ๐Ÿ› Bug Fixes

    • โšก๏ธ Update auto-save-selective-debounce to handle clearing inputs #802
    • Re-initialize onFocus/onBlur handlers if the subscribed field changes #787

    ๐Ÿ›  Type Fixes

    • โšก๏ธ Update FormValues Typescript definition #806


  • v6.5.0

    May 27, 2020

    ๐Ÿ†• New Features

    • ๐Ÿฑ ๐ŸŽ‰๐ŸŽ‰ Forward refs to input component ๐ŸŽ‰๐ŸŽ‰ #608 #141
    • โž• Add modifiedSinceLastSubmit flag to form and field state #799

    ๐Ÿ› Bug Fixes

    • Deduce select type from component prop for select-multiple #793
    • If name prop is passed as undefined to Field component, an error is thrown #777 #450


  • v6.4.0

    March 30, 2020

    โš  As of React v16.13.0, there has been a warning in React Final Form, Redux Form, and Formik. You can read @gaearon's explanation of it here: facebook/react#18178 (comment)

    ๐Ÿš€ This release, in conjunction with final-form@4.19.0, fixes this warning.

    Technically, a peer dependency change should be a major, breaking change, but these two libraries are so tightly coupled, that I'm only making it a "minor" update. Shout at @erikras on Twitter if this upsets you.

    ๐Ÿ› Bug Fix

    • โš  Silent initial field registration to avoid React warning #766 #751


  • v6.3.5

    January 23, 2020

    ๐Ÿ› Bug Fix


  • v6.3.4

    January 22, 2020

    ๐Ÿ› Bug Fixes

    • โž• Add data object to useField/Field #711
    • Submit edge case fix #697 #695
    • โž• Add missing dirtyFieldsSinceLastSubmit to getters #688

    ๐Ÿ›  Typing Fixes

    • โž• Add otherProp to FieldRenderProps interface #716 #398
    • ๐Ÿ›  Fix handleSubmit typings #715#86
    • ๐Ÿ‘Œ Improved type definition for Field #708
    • โž• Added note about the return type of handleSubmit #681 #675


  • v6.3.3

    November 19, 2019

    ๐Ÿ›  Typing Fixes

    • โช Revert "Fix typescript typings in FieldProps (#619)" #679


  • v6.3.2

    November 19, 2019

    ๐Ÿ›  v6.3.1 introduced a bug. v6.3.2 fixes it.

    ๐Ÿ› Bug Fixes

    • Made lazy state getters enumerable #678 #677


  • v6.3.1

    November 18, 2019

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed decorators unsubscribe order #620 #618
    • ๐Ÿ›  Fix issue with inline isEqual causing an infinite rerender loop #603 #517
    • Lazy evaluation of form and field state #596
    • ๐Ÿ›  Fix async act warning #581
    • Pausing validation before unmount #595 #408
    • ๐Ÿ›  Fixed bug with ignoring changes to onChange #572 #569
    • Pass any additional props to custom component #565 #175
    • Pass through multiple value to custom components #545 #544
    • Cleanup onBlur dependencies #546
    • Do not pass undefined type to input #548

    ๐Ÿ›  Typing Fixes

    • ๐Ÿ›  Fix useFormState and useField Flow types #630
    • โž• Add RenderableProps to FormRenderProps #575
    • ๐Ÿ›  Fix typescript typings in FieldProps #619
    • ๐Ÿ›  Fix FormProps['decorators'] #629
    • Pass FormValues type to Decorator #661
    • FieldInputProps extends AnyObject #606
    • โœ‚ Remove Omit from the typescript definitions #589
    • ๐Ÿ‘ Allow typed render props in TS #570

    ๐Ÿ— Build Fixes

    • โœ‚ Remove the version #604


  • v6.3.0

    June 19, 2019

    ๐Ÿ†• New Features

    • ๐Ÿ‘Œ Support for Final Form's new validating flag. Requires final-form@4.16.1. #541

    ๐Ÿ› Bug Fixes

    • ๐Ÿ›  Fixed destroyOnUnregister bug #537
    • โšก๏ธ Use updated value for formatOnBlur format func #465


  • v6.2.1

    June 14, 2019

    Whilst it could be argued that updating a peer dependency is a "breaking change" โ€“ and it would be if it were on a large third party library, like React โ€“ it is the opinion of the library author that, due to the tight coupling between final-form and react-final-form, such a change, especially just for type definitions, is acceptable, even in a "patch" release. Feel free to yell at @erikras on Twitter if you vehemently disagree.

    โšก๏ธ Type Updates