Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 21, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
formik (source) 2.0.4 -> 2.2.9 age adoption passing confidence

Release Notes

formium/formik

v2.2.9

Compare Source

Patch Changes

v2.2.8

Compare Source

Patch Changes

v2.2.7

Compare Source

Patch Changes
  • e50040a #​2881 Thanks @​jinmayamashita! - Prevent calling getSelectedValues when the element has not options

  • 31405ab #​3201 Thanks @​artola! - Fixes regression that resulted in error update race condition from when using validateOnMount

  • c2d6926 #​2995 Thanks @​johnrom! - Allow explicitly setting <form action> to empty string (#​2981). Note: previous code which passed an empty string would result in a noop (simply appending # to the url), but this will now result in a form submission to the current page.

v2.2.6

Compare Source

Patch Changes

v2.2.5

Compare Source

Patch Changes

v2.2.4

Compare Source

Patch Changes

v2.2.3

Compare Source

Patch Changes

v2.2.2

Compare Source

Patch Changes

v2.2.1

Compare Source

Patch Changes

v2.2.0

Compare Source

Minor Changes
  • 4148181 #​2794 Thanks @​jaredpalmer! - setValue can now optionally accept a function as a callback, exposing React.SetStateAction functionality. Previously, only the entire object was
    allowed which caused issues with stale props.

    setValues(prevValues => ({...prevValues, ... }))

v2.1.7

Compare Source

Patch Changes

v2.1.6

Compare Source

v2.1.5

Compare Source

v2.1.4

Compare Source

v2.1.3

Compare Source

v2.1.2

Compare Source

v2.1.1

Compare Source

Patches
  • Update website: d1059c8
  • Small spelling error: #​2161
  • Correctly handle single checkboxes and grouped ones values: #​2159. Fixed a bug when value was not specified on a checkbox as well as when there is just one checkbox.
  • Adds a community article: #​2157
  • Update contributing guidelines start step: #​2158
  • Force FieldArray to use latest values for validation: #​2166
Credits

Huge thanks to @​wallymathieu, @​eliamaino-fp, and @​mrmuhammadali for helping!

v2.1.0

Compare Source

Minor Changes
  • Add FieldHelpers object to the array returned by useField: #​2124. This
    exposes three helper functions to allow you to imperatively change the
    field in question:

    1. setValue(value: any)
    2. setTouched(value: boolean)
    3. setError(value: string)

    Before

    const MyInput = (props) => {
     const formik = useFormikContext() 
     const [field, meta] = useField(props)
     const handleThing = () => {
        formik.setFieldValue(props.name, 'boop') 
     }
     // ...
    }

    After

    const MyInput = (props) => {
     const [field, meta, helpers] = useField(props)
     const handleThing = () => {
        helpers.setValue('boop') 
     }
     // ...
    }
Credits

Huge thanks to @​drivasperez for helping!

v2.0.11

Compare Source

Patches
  • Keep empty array values on FieldArray: #​2144
Credits

Huge thanks to @​viniciusdacal for helping!

v2.0.10

Compare Source

TS Patch

  • Fix useField<T> generic.

v2.0.9

Compare Source

Patches
  • Hotfix: Revert throwing combined errors: #​2103
  • Abort submit if instance of real Error: #​2104
  • Remove inline cDU usage in FieldArray: #​2114
  • Remodel FieldArray validation side effect to cDU: #​2115
  • Allow forced validation to run anywhere #​2116
  • Handle promise rejection in handleSubmit #​2136
  • Fix unhandled promise exception in low priority validation #​2119

v2.0.8

Compare Source

Patches
  • Hotfix: Revert throwing combined errors: #​2103
  • Abort submit if instance of real Error: #​2104
  • Remove inline cDU usage in FieldArray: #​2114
  • Remodel FieldArray validation side effect to cDU: #​2115

v2.0.7

Compare Source

Improvements

  • Massive perf boost over 2.0.6! We now save renders by comparing errors more efficiently in useFormik/Formik.
  • FastField is now even faster. We fixed up our implementation of shouldComponentUpdate by refactoring the component away from using static contextType and back to using the connect() higher order component.

Bug fixes

  • Fixed regression where dirty is wasn't re-evaluated after resetForm()

  • Fixed regression where handleChange would explode when event.target didn't exist (e.g. event.currentTarget

  • If there are validation errors while calling submitForm(), the promise will now rejects with errors (and of course abort the submit). Previously, it would abort the submit and resolve. The nuance is hard to describe so here is the difference.

    Before (2.0.6)

     submitForm() // imagine there are some Yup validation errors
      .then(() => console.log("abort submit, did not call onSubmit, and end up here"))
      .catch(() => console.log("abort submit, did not call onSubmit, but only because of a runtime error"));

    After (2.0.7)

     submitForm() // imagine there are some Yup validation errors
      .then(() => console.log("executed onSubmit"))
      .catch((err) => console.log("aborted submit attempt"));

    2.0.6: https://codesandbox.io/s/gracious-noether-bu8u6
    2.0.7: https://codesandbox.io/s/objective-perlman-jxhuq

Commits

v2.0.6

Compare Source

Bugfix

  • Change onSubmit's type signature to accept Promise<any>. This allows folks to return a promise that returns something (which is pretty common). Sorry about that folks.

Commits

  • Generate 2.0.6 docs e933b9c
  • Correct 2.0.5 docs 67e9071
  • Change type signature of onSubmit to accept Promise 2738bbc

v2.0.5

Compare Source

Bugfixes

  • Changed onSubmit behavior to mimic v1 if the function is synchronous. This means fixes a bug where isSubmitting was never toggled. To summarize: If onSubmit is async, then Formik will automatically set isSubmitting to false on your behalf once the submission is completed. This means you do NOT need to call formikBag.setSubmitting(false) manually in v2. HOWEVER, if your onSubmit function is synchronous (e.g. v1), then you need to still call setSubmitting(false) on your own. (#​1987)
  • Fix checkbox bug with null value (#​2027)
  • Update validateFormWithLowPriority with to use fresh values (#​2025)

Commits


Configuration

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

🚦 Automerge: Enabled.

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
Copy link
Author

renovate bot commented Nov 21, 2019

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot force-pushed the renovate/formik-2.x branch from ad6f51a to af9d8c3 Compare November 21, 2019 21:34
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.0.5 fix(deps): update dependency formik to v2.0.6 Nov 21, 2019
@renovate renovate bot force-pushed the renovate/formik-2.x branch 19 times, most recently from 979467d to 8f01701 Compare November 28, 2019 04:53
@renovate renovate bot force-pushed the renovate/formik-2.x branch 8 times, most recently from 24b9843 to d4d62ce Compare December 2, 2019 04:23
@renovate renovate bot force-pushed the renovate/formik-2.x branch 9 times, most recently from 646eea6 to 87eccde Compare January 21, 2020 03:46
@renovate renovate bot force-pushed the renovate/formik-2.x branch 4 times, most recently from 536a84b to ee85ba9 Compare January 28, 2020 15:07
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.1.2 fix(deps): update dependency formik to v2.1.3 Jan 28, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from ee85ba9 to 829a07a Compare February 6, 2020 18:19
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.1.3 fix(deps): update dependency formik to v2.1.4 Feb 6, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from 829a07a to e7c5cde Compare July 2, 2020 05:05
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.1.4 Update dependency formik to v2.1.4 Jul 2, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from e7c5cde to 3fbca70 Compare July 14, 2020 18:00
@renovate renovate bot changed the title Update dependency formik to v2.1.4 Update dependency formik to v2.1.5 Jul 14, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from 3fbca70 to 01c1f80 Compare October 29, 2020 05:06
@renovate renovate bot changed the title Update dependency formik to v2.1.5 fix(deps): update dependency formik to v2.2.1 Oct 29, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from 01c1f80 to a170acf Compare November 28, 2020 13:00
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.2.1 fix(deps): update dependency formik to v2.2.5 Nov 28, 2020
@renovate renovate bot force-pushed the renovate/formik-2.x branch from a170acf to 069ec97 Compare January 6, 2021 18:55
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.2.5 fix(deps): update dependency formik to v2.2.6 Jan 6, 2021
@renovate renovate bot force-pushed the renovate/formik-2.x branch from 069ec97 to 6f54588 Compare June 6, 2021 21:00
@renovate renovate bot changed the title fix(deps): update dependency formik to v2.2.6 fix(deps): update dependency formik to v2.2.9 Jun 6, 2021
@renovate
Copy link
Author

renovate bot commented Mar 24, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant