Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency final-form to v4 #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update dependency final-form to v4 #13

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 11, 2019 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
final-form 3.0.0 -> 4.20.9 age adoption passing confidence

Release Notes

final-form/final-form

v4.20.9

Compare Source

v4.20.8

Compare Source

  • Merge pull request #​461 from antonvialibri1/fix-for-array-checkboxes-inputs-after-regression-introduced-in-version-4.20.3 b905214
  • Merge pull request #​446 from final-form/dependabot/npm_and_yarn/follow-redirects-1.14.8 24bc8b3
  • Merge pull request #​452 from final-form/dependabot/npm_and_yarn/minimist-1.2.6 b084b4b
  • Merge pull request #​454 from final-form/dependabot/npm_and_yarn/simple-get-3.1.1 0499149
  • Merge pull request #​466 from final-form/dependabot/npm_and_yarn/decode-uri-component-0.2.2 ec23212
  • Merge pull request #​468 from final-form/dependabot/npm_and_yarn/json5-1.0.2 a5063e4
  • Merge branch 'huan086-feature/fix-up-field-state' 3b49609
  • Merge branch 'feature/fix-up-field-state' of github.com:huan086/final-form into huan086-feature/fix-up-field-state b666d1c
  • Bump json5 from 1.0.1 to 1.0.2 fef51c5
  • Bump decode-uri-component from 0.2.0 to 0.2.2 5464d69
  • Fix for issue #​456 - Fixes unwanted breaking change for array input names introduced in v4.20.3 (a3575ef) - v4.20.2 used to work fine 3e47a6b
  • Bump simple-get from 3.1.0 to 3.1.1 fba79fa
  • Bump minimist from 1.2.5 to 1.2.6 a75117b
  • Bump follow-redirects from 1.14.4 to 1.14.8 6ace61a
  • If mutator creates a new field in MutableState for keeping the field state of a renamed field, set the blur, focus and change function of InternalFieldState when registerField is called. 33e551f

v4.20.7

Compare Source

  • Make allValues argument optional on type FieldValidator (#​394)
  • Prevent formState.values from initializing to undefined (#​450)

v4.20.6

Compare Source

Bug Fixes

  • Better fix for async error bug #​441

v4.20.5

Compare Source

Bug Fixes

  • Don't clear async errors between validations #​440

v4.20.4

Compare Source

Oops. Apologies!

  • Remove engines from package.json #​434

v4.20.3

Compare Source

Bug Fixes

Type Fixes

  • Fix documentation and TypeScript definition of FormApi.restart #​425
  • TypeScript: Make restart and initialize take InitialFormValues instead of FormValues #​429 #​389

v4.20.2

Compare Source

Bug Fixes

  • Notify form (#​386) #​383
  • Do not use defaultValue in register call if formState already has it (#​372)
  • Fix validating field state when blurring before the promise is resolved (#​369)
  • Fix reset in onSubmit (#​363) #​362
  • Fix a crash when renamed field is unregistered (#​385) #​384
  • Force field level initialization over form level (#​364)

Type Fixes

v4.20.1

Compare Source

Hi, @​erikras here. The primary purpose for adding scarf as a dependency to this library was to gain some insights into just who is using this library. Nothing but the IP addresses of the computers running the npm install were ever recorded, which were back referenced to determine corporation identity. It was never "malware", but for sure it broke the contract assumption of "I can run npm install without anyone collecting data about me". Every day that assumption is more tenuous, as the 21st century internet continues the trend towards the default assumption being "someone is collecting data about me". But I, personally, don't feel right participating in that trend. The month or so that I had scarf installed confirmed that the largest Silicon Valley giants are using this library. Further spying will not produce more value. I would like to apologize for violating your trust.

That said, the psychosocial rot that is consuming Open Source is the broken funding model. If each of you would request the equivalent of one hour of your salary every month to go to libraries you use (and save you way more than one hour per month), we OSS devs would feel less compelled to search for funding solutions. Please consider adding a line item... ❤️

Changes

v4.20.0

Compare Source

Features

  • Add restart() API method to reset all form and field state #​348 #​333
  • Add modifiedSinceLastSubmit to field and form state #​345 #​215

Bug Fixes

  • Fix validation preventing update of form state submit errors #​325
  • Fix missing field state argument if validator function is wrapped with unknown number of args #​337

Type Fixes

  • Type safety improvements to FieldState and FormApi #​318
  • Add InitialValues type default to Partial<FormValues> #​332 #​314

v4.19.1

Compare Source

Bug Fixes

v4.19.0

Compare Source

Features

Optimizations

  • Optimize toPath method by caching results #​329

v4.18.7

Compare Source

Bug Fixes

  • Fix field initial value validation #​301 #​296
  • Stop resubmitting when validator throw an error and log the error instead #​309 #​308
  • Reinitialize non-registered values with keepDirtyOnReinitialize #​311

v4.18.6

Compare Source

Bug Fixes

Type Fixes

  • Fixed config typing form mutators #​275

v4.18.5

Compare Source

Bug Fixes

  • No need to run validation on field register without validator #​267

v4.18.4

Compare Source

Bug Fixes

That one has been causing problems for a long time. Thanks @​shrugs!

also....

🎉🎉🎉 ➡️ New Docs Site ⬅️ 🎉🎉🎉

v4.18.3

Compare Source

Bug Fixes

  • Fixed bug where changing field-level validation would not update other fields (#​263)
  • Better compatibility with IE11 (#​260)

Type Fixes

  • Use SubmissionErrors type alias consistently (#​262)
  • Better TypeScript typing for FieldState.initial (#​251)
  • Improve setConfig TypeScript typing (#​259)
  • Improve ARRAY_ERROR & FORM_ERROR TypeScript types (#​254)

v4.18.2

Compare Source

  • Rebind event handlers when field is renamed b0d9bea

v4.18.1

Compare Source

  • Fix bug when mutator removes field state #​246

v4.18.0

Compare Source

Author's note: While technically this is a breaking change, it's only removing an internal API (made for final-form-array) on a Monday morning that was first published less than 48 hours earlier, on Saturday afternoon. If you spent all day Sunday rewriting a project to use the ultimately unneeded forceUpdate API, then I do sincerely apologize. You should change fieldState.forceUpdate=true to fieldState.lastFieldState=undefined to get the same effect. Feel free to yell at @​erikras on Twitter if not bumping the major version number for this release outrages you.

v4.17.0

Compare Source

New Features

  • Added internal forceUpdate flag for fields for final-form-arrays' mutators. #​244

v4.16.2

Compare Source

Bug Fixes

Type Fixes

  • Fixed TS GetFieldValidator #​237

v4.16.1

Compare Source

🤦‍♂️

Flow Fixes

  • Actually export validating in FieldState for flow 26f186e

v4.16.0

Compare Source

New Features

  • The long awaited (no pun intended) validating flag on each field #​235, inspired by #​232
  • Added destroyOnUnregister getter and setter #​233
  • Throw informative error if attempt to reset() when submitting #​229

Bug fixes and maintenance

  • Fix typo in error message #​231
  • Lookup version at build time #​230

v4.15.0

Compare Source

TypeScript Features

v4.14.1

Compare Source

Type Fixes

Just some minor type fixes from v4.14.0.

v4.14.0

Compare Source

New features!

  • 💥 Strongly typed form values for Flow and Typescript 💥 #​223

v4.13.1

Compare Source

Bug Fixes

  • Safe field iteration. There was an obscure bug where Final Form would fall over if a field got unregistered during the notification process. #​221 #​26

v4.13.0

Compare Source

New Features

  • Added beforeSubmit and afterSubmit callbacks to FieldConfig #​216

Bug Fixes

Typing Fixes

  • Dynamically generate ConfigKey using keyof #​208
  • Improvements to the Typescript types around FormData #​209

v4.12.0

Compare Source

🎉 New Features 🎉

  • The argument to initialize can now optionally be a function that takes the current values and returns the new initial values. #​199
  • Added defaultValue and initialValue values to FieldConfig, thus allowing fields to be initialized at registration time. #​200 https://github.com/final-form/react-final-form/issues/387
  • Added modified flag for all fields. A field becomes modified the first time its value changes. Previously, with dirty, if the user returned the value to the initial value, the form state had no evidence that the value had ever changed. This is what modified provides. #​201

v4.11.1

Compare Source

Bug Fixes

v4.11.0

Compare Source

Types

Bug Fixes

  • Rely less on onSubmit.length to determine callback style #​165
  • Remove values when setting them to undefined #​176
  • Rethrow submit errors so promise rejects #​170 #​156

New Features

  • Added submitting to FieldState #​173 #​172
  • Use @babel/helpers helpers instead of bundled ones #​167

v4.10.0

Compare Source

New Features

  • New renameField mutator #​153
  • Field state now sent to field-level validator functions #​125

v4.9.1

Compare Source

Bug Fixes

  • Ensured calculated form state – e.g. touched, visited, dirtyFields – returned from getState() #​150

v4.9.0

Compare Source

Features

Bug Fixes

  • Made submitting and validating flags flip back to false on Promise rejection. #​148 #​138
  • Made reset() also reset submitError #​141 #​140

v4.8.3

Compare Source

Bug Fixes

v4.8.2

Compare Source

Type Fixes

  • Fixed some of the Typescript types #​136

v4.8.1

Compare Source

Bug Fixes

  • Originally, 🏁 Final Form was written with an implicit assumption that you could not update the values of fields that were not registered. Several users have questioned this assumption, and rightfully so. Why limit the flexibility of the library? Nothing was being gained by that assumption. So that is gone now. You can form.change('field', 'value') for any field. regardless of whether or not it is registered. #​134 #​102 https://github.com/final-form/final-form-calculate/issues/15
  • Exchanged use of Object.entries (which is way more useful) for the better supported Object.keys. #​135

v4.8.0

Compare Source

New Features

v4.7.3

Compare Source

🤦‍♂️

Burned through a few versions because NPM was acting wonky. I wouldn't necessarily trust v4.7.1 or v4.7.2, even though the only thing that changed was the version number.

v4.7.2

Compare Source

v4.7.1

Compare Source

Typing Fixes

  • Fixed problem with exported configKeys value. Only used internally to interact with react-final-form.

v4.7.0

Compare Source

New Features

v4.6.2

Compare Source

Bug Fixes

  • Fixed a bug in hadValidationErrors that was reporting true when there were no errors. #​121 #​123 #​126

v4.6.1

Compare Source

New API

  • New form.isValidationPaused() API needed to fix a bug in 🏁 React Final Form. #​119

v4.6.0

Compare Source

Bug fixes

  • Improved performance by halting notifications when validation is paused, such as when many fields are being registered on first render. #​118

v4.5.2

Compare Source

Type Fixes

  • Type signature was wrong for reset() on both Flow and Typescript. #​114

v4.5.1

Compare Source

v4.5.0 was broken. 😳

Features

Bug Fixes

v4.4.0

Compare Source

Bug Fixes

  • Fixed very annoying bug where clearing one field-level validation error would erase them all. #​94 #​75

New Features

  • New way to set an error on an array of fields. #​92
import { ARRAY_ERROR } from 'final-form'

...

errors.items = []
errors.items[ARRAY_ERROR] = 'You need some items'
  • New form.getFieldState(fieldName) API to inquire about the state of a given field. #​93 #​91

v4.3.1

Compare Source

Bug Fixes

v4.3.0

Compare Source

New Features

Flow Fixes

v4.2.1

Compare Source

Bug Fixes

  • Reset submit state (e.g. submitFailed, etc.) when form.reset() is called. #​84 #​72
  • Await async validation before submission #​83 #​82

v4.2.0

Compare Source

New Features

  • You can now pauseValidation() and resumeValidation() to have finer control over when the automatic validation is run. #​74 #​73

v4.1.0

Compare Source

Bug Fixes

Flow Fixes

New Features

v4.0.4

Compare Source

Typescript fixes

  • Ensure mutators is defined to avoid bad strongly typed developer casting experience #​68

v4.0.3

Compare Source

For some reason v4.0.2 did not have the changes it was supposed to have... 🤷‍♂️

v4.0.2

Compare Source

Typescript fixes

v4.0.1

Compare Source

Typescript Fixes

  • Added typescript regression tests and fixed some minor type errors #​61

Bug Fixes

  • submitFailed is now true if the submission failed because of sync validation errors. #​64 #​63

v4.0.0

Compare Source

⚠️ BREAKING CHANGE ⚠️

It's fairly minor, but when you register a field now, rather than provide a field-level validation function, now you must provide a function that returns the validation function. The migration is pretty trivial:

v3.x.x
form.registerField(
  'firstName',
  fieldState => { // do something with field state },
  fieldSubscription,
  {
    validate: value => { // return error }
  }
)
v4.x.x
form.registerField(
  'firstName',
  fieldState => { // do something with field state },
  fieldSubscription,
  {
    validate: () => value => { // return error }
//            ^^^^^--- ADD THIS 👀
  }
)

v3.1.0

Compare Source

New Features

  • A new dirtySinceLastSubmit flag is available to both the form and fields, which lets you know if the values have change since the last submit occurred, whether successful or not. This is particularly useful for hiding submission errors once the user has attempted to fix them. #​57 #​4 #​38 #​48

v3.0.1

Compare Source

Typescript

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/final-form-4.x branch 5 times, most recently from 0c62869 to 0aebcae Compare July 16, 2019 12:19
@renovate renovate bot force-pushed the renovate/final-form-4.x branch 3 times, most recently from 20f4534 to 5e53a17 Compare August 15, 2019 09:59
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 5e53a17 to 574a656 Compare November 12, 2019 06:01
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 574a656 to 4a0a8a2 Compare February 8, 2020 22:52
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 4a0a8a2 to 477d14a Compare May 2, 2020 19:56
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 477d14a to 35a9285 Compare July 2, 2020 03:51
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 35a9285 to a249765 Compare April 26, 2021 14:22
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from a249765 to d07b438 Compare October 18, 2021 19:24
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from d07b438 to 933d7eb Compare February 6, 2022 21:20
@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 933d7eb to 8a4d257 Compare May 15, 2022 18:33
@renovate
Copy link
Contributor Author

renovate bot commented Mar 12, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@renovate renovate bot force-pushed the renovate/final-form-4.x branch from 8a4d257 to 7510e84 Compare March 16, 2023 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants