All Versions
12
Latest Version
Avg Release Cycle
22 days
Latest Release
31 days ago

Changelog History
Page 1

  • v6.3.5

    January 23, 2020

    πŸ› Bug Fix

    v6.3.4...v6.3.5

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

  • v6.3.3

    November 19, 2019

    πŸ›  Typing Fixes

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

    v6.3.2...v6.3.3

  • 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...v6.3.2

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

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

  • 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

    v6.2.0...v6.2.1

  • v6.2.0

    June 14, 2019

    πŸ›  TypeScript fixes

    • 0️⃣ Use the same default for FormValues type in all declared types (#525)
    • 0️⃣ Replace empty object default type with any object (#526)
    • ♻️ Refactor getContext back to a simple context file (#524)

    πŸ†• New Features

    • Strongly typed field values (#530)
    • βž• Added tsx generic typings for Field, Form, and FormSpy components (#522)

    For Typescript users, you can take advantage of JSX Generics, so you can specify the type of your form values or field value directly in the JSX call to Form, Field, or FormSpy. For Form, it will even infer the form values type if you provide initialValues.

    Behold this code:

    interface MyValues { firstName: stringlastName: string}const initialValues: MyValues = { firstName: 'Erik', lastName: 'Rasmussen'}const onSubmit = (values: MyValues) =\> { ajax.send(values) }
    
    {/\* Typescript will complain if the type of initialValues is not the same as what is accepted by onSubmit\*/} \<Form onSubmit={onSubmit} initialValues={initialValues}\> {({ handleSubmit, values }) =\> { // πŸ’₯ Type of values is inferred from the type of initialValues πŸ’₯return ( \<form onSubmit={handleSubmit}\> {/\* 😎 Field values are strongly typed using JSX generics 😎 \*/} \<Field\<string\> name="firstName" component={TextInput} /\> \<Field\<string\> name="lastName" component={TextInput} /\> \<Field\<number\> name="age" component={NumberInput} /\> \<button type="submit"\>Submit\</button\> \</form\> ) }} \</Form\>
    

    v6.1.0...v6.2.0

  • v6.1.0

    June 11, 2019

    πŸ†• New Features

    • πŸ‘ Allowed swappable final-form APIs #520
    • 🍱 πŸ’₯ Strongly typed form values for Flow and Typescript πŸ’₯ #516

    Usage:

    import { withTypes, Field } from 'react-final-form'type MyValues = { email: string, password: string}const { Form } = withTypes\<MyValues\>() \<Form onSubmit={onSubmit}\> {({ handleSubmit, values }) =\> { // values are of type MyValues }} \</Form\>
    

    Edit Strongly Typed Form Values with 🏁 React Final Form

    Housekeeping

    • βœ‚ Remove context export #515
    • βœ… Simplify slightly logic around keeping latest value in ref #513

    v6.0.1...v6.1.0

  • v6.0.1

    May 29, 2019

    πŸ› Bug Fixes

    • No rerender on validateFields change #504 #502

    πŸ›  Type Fixes

    • πŸ›  Fix Flow typings for UseFieldConfig and FieldProps #503
    • βž• Added back flow types that got removed #505 #500
    • ⚑️ Update Types to make useField's options optional #499

    v6.0.0...v6.0.1