Skip to content

Releases: final-form/react-final-form

v6.5.1

13 Jul 17:07
v6.5.1
Compare
Choose a tag to compare

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...v6.5.1

v6.5.0

27 May 15:03
v6.5.0
Compare
Choose a tag to compare

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...v6.5.0

v6.4.0

30 Mar 19:51
v6.4.0
Compare
Choose a tag to compare

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...v6.4.0

v6.3.5

23 Jan 09:59
v6.3.5
Compare
Choose a tag to compare

Bug Fix

v6.3.4...v6.3.5

v6.3.4

22 Jan 08:44
v6.3.4
Compare
Choose a tag to compare

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...v6.3.4

v6.3.3

19 Nov 10:53
v6.3.3
Compare
Choose a tag to compare

Typing Fixes

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

v6.3.2...v6.3.3

v6.3.2

19 Nov 09:31
v6.3.2
Compare
Choose a tag to compare

v6.3.1 introduced a bug. v6.3.2 fixes it.

Bug Fixes

  • Made lazy state getters enumerable #678 #677

v6.3.1...v6.3.2

v6.3.1

18 Nov 09:44
v6.3.1
Compare
Choose a tag to compare

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...v6.3.1

v6.3.0

19 Jun 10:46
v6.3.0
Compare
Choose a tag to compare

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...v6.3.0

v6.2.1

14 Jun 13:29
v6.2.1
Compare
Choose a tag to compare

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

  • Updated to FF@4.15.0 to get typed FieldState ab2e970

v6.2.0...v6.2.1