-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
fix(deps): update dependency formik to v2 #3143
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/formik-2.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 10, 2024 10:32
5a922c1
to
879973b
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 10, 2024 10:56
879973b
to
9bb06aa
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 10, 2024 11:15
9bb06aa
to
9b051a9
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 10, 2024 11:21
9b051a9
to
7032405
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 12, 2024 09:58
7032405
to
535234a
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 12, 2024 10:45
535234a
to
dd9d65c
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 12, 2024 10:48
dd9d65c
to
1ef5e63
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 12, 2024 19:55
1ef5e63
to
6ded0e8
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 14, 2024 07:36
6ded0e8
to
14b0a16
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 14, 2024 10:29
14b0a16
to
0bc2756
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 18, 2024 06:20
0bc2756
to
8515031
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 18, 2024 09:03
8515031
to
127ee0b
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 18, 2024 09:57
127ee0b
to
70543f9
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 19, 2024 16:13
70543f9
to
fdbfed8
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 19, 2024 16:53
fdbfed8
to
e4e56f7
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 20, 2024 14:21
e84e054
to
8c6cdac
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 23, 2024 11:54
8c6cdac
to
808948e
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 23, 2024 13:32
808948e
to
f9d7ead
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 23, 2024 17:38
f9d7ead
to
fd54449
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 23, 2024 18:30
fd54449
to
e7e19f0
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
September 24, 2024 09:55
e7e19f0
to
14b477e
Compare
Anas12091101
force-pushed
the
renovate/formik-2.x
branch
from
October 14, 2024 15:52
24da22d
to
61094e4
Compare
We were using refs in B2BPurchaseForm(Formik) Formik's Official Discussion around this => jaredpalmer/formik#2208 |
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
9 times, most recently
from
November 16, 2024 16:06
e81998d
to
745627f
Compare
renovate
bot
force-pushed
the
renovate/formik-2.x
branch
from
November 16, 2024 18:50
745627f
to
184b35b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.5.1
->^2.0.0
Release Notes
jaredpalmer/formik (formik)
v2.4.6
Compare Source
v2.4.5
Compare Source
Patch Changes
d7db9cd
#3860 Thanks @patik! - Add missing dependency@types/hoist-non-react-statics
, closes #3837fe4ed7e
#3501 Thanks @markspolakovs! - Markformik
as side-effect free inpackage.json
v2.4.4
Compare Source
Patch Changes
41720c2
#3862 Thanks @yazaldefilimonepinto! - ForwardclassName
for custom components used withField
da58b29
#3858 Thanks @alaanescobedo! - Remove use of deprecatedStatelessComponent
type in favor ofFunctionComponent
5c01ee7
#3872 Thanks @rajpatelbot! - FIX: Fixed resetForm function dependency issuev2.4.3
Compare Source
Patch Changes
9e0a661
#3843 Thanks @bonimba! - Fix FormikHelper and FieldHelperProps typesv2.4.2
Compare Source
Patch Changes
96280d3
#3817 Thanks @probablyup! - Updated internal types to support React 18.v2.4.1
Compare Source
Patch Changes
2b194c2
#3808 Thanks @NagaiKoki! - fix type of setFieldValue function708bcb2
#3813 Thanks @probablyup! - RevertFieldArray
"shouldComponentUpdate" performance optimization. As it turns out, it's a common use case to have JSX controlled via non-Formik state/props inside ofFieldArray
, so it's not safe to cancel re-renders here.187e47d
#3815 Thanks @probablyup! - Revert Yup transform support for the time being, this may be re-introduced in a future release under an opt-in prop.v2.4.0
Compare Source
Minor Changes
2f53b70
#3796 Thanks @probablyup! - Add support for Yup "transforms".v2.3.3
Compare Source
Patch Changes
f075a0c
#3798 Thanks @probablyup! - Fixed the use of generics for theArrayHelpers
type such thatany[]
is the default array type and for each individual method the array item type can be overridden if necessary.v2.3.2
Compare Source
Patch Changes
f086b5a
#3237 Thanks @pieplu! - ChangedgetIn
to return undefined when it can't find a value AND a parent of that value is "falsy" ( "" / 0 / null / false )6d8f018
#3792 Thanks @probablyup! - Update the type forsetFieldValue
to reflect the returnedPromise
and potential returned error(s).v2.3.0
Compare Source
Minor Changes
73de78d
#3788 Thanks @probablyup! - Added typescript generics toArrayHelpers
interface and its methods so that users who use TypeScript can set the type for their arrays and have type safety on array utils. I have also gone ahead and made supplying a type for the generic optional for the sake of backwards compatibility so any existing TS code that does not give a type for the FieldArray will continue to work as they always have.39a7bf7
#3786 Thanks @probablyup! - Yup by default only allows for cross-field validation within thesame field object. This is not that useful in most scenarios because
a sufficiently-complex form will have several
yup.object()
in theschema.
However, Yup offers something called
context
which can operate acrossthe entire schema when using a \$ prefix:
With this change, you may now validate against any field in the entire schema,
regardless of position when using the \$ prefix.
v2.2.10
Compare Source
Patch Changes
22e236e
#3784 Thanks @probablyup! - Improve performance of theFieldArray
component by adding ashouldComponentUpdate
check; this should help avoid unnecessary re-renders which may affect the performance of a form.bc9cb28
#3785 Thanks @probablyup! - Fixed field error state for array fields that have an error and become empty through an API likearrayHelpers.remove
.The prior behavior resolved the field error to
[undefined]
, now it is simplyundefined
.9cbf150
#3787 Thanks @probablyup! - Fix infinite loop issue inField
when field helpers (setTouched
, etc) are used as an argument inReact.useEffect
.9c75a9f
#3780 Thanks @probablyup! - Fixed an issue with array field errors being incorrectly split into an array of individual characters instead of an array of error strings.35fa4cc
#3783 Thanks @probablyup! - Fix validation of deep.dot.path field references when using thevalidateField
API.v2.2.9
Compare Source
Patch Changes
ca60ef9
#3227 Thanks @johnrom! - Bump lodash and lodash-es to latest versions.v2.2.8
Compare Source
Patch Changes
3a9c707
#3203 Thanks @hixus! - Fixes type of setError value as it is same as setFieldError messagev2.2.7
Compare Source
Patch Changes
e50040a
#2881 Thanks @jinmayamashita! - Prevent calling getSelectedValues when the element has not options31405ab
#3201 Thanks @artola! - Fixes regression that resulted in error update race condition from when usingvalidateOnMount
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
d4314a1
#2955 Thanks @jkbktl! - fix(docs): fix link to docs in console warningv2.2.5
Compare Source
Patch Changes
ebad985
#2891 Thanks @jaredpalmer! - Remove low-priority validation implementation0dfa23b
#2889 Thanks @jaredpalmer! - Fixed botched typescript builds including scheduler typesv2.2.4
Compare Source
Patch Changes
199e77a
#2882 Thanks @umidbekkarimov! - ValidatesetFieldTouched
with high priorityv2.2.3
Compare Source
Patch Changes
e0a28e6
#2867 Thanks @umidbekkarimov! - Fix low priority validation for browser password autofill.958d67c
#2874 Thanks @maddhruv! - fix FastField initial value when input type is radio or checkboxv2.2.2
Compare Source
Patch Changes
00f95ec
#2854 Thanks @umidbekkarimov! - Fix low priority validation race condition.v2.2.1
Compare Source
Patch Changes
e04886d
#2820 Thanks @wellyshen! - Fixed bug with scheduler andvalidateFormWithLowPriority
method not be scheduled correctlyv2.2.0
Compare Source
Minor Changes
4148181
#2794 Thanks @jaredpalmer! -setValue
can now optionally accept a function as a callback, exposingReact.SetStateAction
functionality. Previously, only the entire object wasallowed which caused issues with stale props.
v2.1.7
Compare Source
Patch Changes
bda9f41
#2785 Thanks @jaredpalmer! - Replace all instances of the deprecated React.SFC type with React.FCv2.1.6
Compare Source
v2.1.5
Compare Source
Bugfixes
prepareDataForValidation
. (#2265)LowPriority
fromscheduler
innerRef
type signature (#2325)handleChange
/handleBlur
typings (#2472)@typescript-eslint/unbound-method
warning.Internal
Legal
Commits
prepareDataForValidation
. (#2265)v2.1.4
Compare Source
v2.1.3
Compare Source
Patches
8f998ae
initialValues
and avalue
wasn't specified at /. Now we are nicer about it, and set the nextvalue
totrue
instead of throwing.67ff970
4ff1c5c
Credits
Huge thanks to @mackness, @JanCizmar, @is2ei, @leonvisscher, @stephan281094, and @brentvatne for helping!
v2.1.2
Compare Source
Patches
587c5ee
7173d74
4b23009
7f00fd6
9c1b0d0
validate
: #2195Credits
Huge thanks to @BjoernRave, @emrosenf, @kristenmills, @dremex, @zachintosh, @deini, @brunohkbx, @Menardi, @gwn, @fabb, and @jamesmosier for helping!
v2.1.1
Compare Source
Patches
d1059c8
value
was not specified on a checkbox as well as when there is just one checkbox.FieldArray
to use latest values for validation: #2166Credits
Huge thanks to @wallymathieu, @eliamaino-fp, and @mrmuhammadali for helping!
v2.1.0
Compare Source
Minor Changes
Add
FieldHelpers
object to the array returned byuseField
: #2124. Thisexposes three helper functions to allow you to imperatively change the
field in question:
setValue(value: any)
setTouched(value: boolean)
setError(value: string)
Before
After
Credits
Huge thanks to @drivasperez for helping!
v2.0.11
Compare Source
Patches
Credits
Huge thanks to @viniciusdacal for helping!
v2.0.10
Compare Source
TS Patch
useField<T>
generic.v2.0.9
Compare Source
Patches
v2.0.8
Compare Source
Patches
v2.0.7
Compare Source
Improvements
shouldComponentUpdate
by refactoring the component away from usingstatic contextType
and back to using theconnect()
higher order component.Bug fixes
Fixed regression where
dirty
is wasn't re-evaluated afterresetForm()
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)
After (2.0.7)
2.0.6: https://codesandbox.io/s/gracious-noether-bu8u6
2.0.7: https://codesandbox.io/s/objective-perlman-jxhuq
Commits
17d82bc
ec1d679
c5ec709
2b6f71e
39bfbfb
5c59dbe
f4ff028
9da3288
37870bf
4ac6186
v2.0.6
Compare Source
Bugfix
Promise<any>
. This allows folks to return a promise that returns something (which is pretty common). Sorry about that folks.Commits
e933b9c
67e9071
2738bbc
v2.0.5
Compare Source
Bugfixes
onSubmit
behavior to mimic v1 if the function is synchronous. This means fixes a bug whereisSubmitting
was never toggled. To summarize: IfonSubmit
is async, then Formik will automatically setisSubmitting
tofalse
on your behalf once the submission is completed. This means you do NOT need to callformikBag.setSubmitting(false)
manually in v2. HOWEVER, if youronSubmit
function is synchronous (e.g. v1), then you need to still callsetSubmitting(false)
on your own. (#1987)validateFormWithLowPriority
with to use fresh values (#2025)Commits
a78bbff
430f6cc
af0c7d0
d0d7602
b04a762
8dbaaba
isSubmitting
behaviour to mimic v1 (#1987)3ce6551
c0fe1b9
e386371
eb2029d
d78266f
0f54fb8
aa7fbdb
d0b5b07
02c303f
5916ac0
55cbfd3
8c08a63
28c9242
4b52d26
189256d
11a4bee
7940fee
v2.0.4
Compare Source
Bugfixes
prepareDataForValidation
work with instances (#1949)ec7810a
. this fixed a regression where people were having issues when keeping wonky objects likeMoment()
as values.scheduler
dep.Internal
Commits
5bae8e0
5553720
343c4ee
86b61bb
7fc52e1
8286190
82775fa
FormikActions
rename toFormikHelpers
(#1988)f80d9c6
76ec8de
a4ebf84
a2b66c5
d90149e
56c0a80
.min()
method tomax()
(#1959)654b97f
e2c2d08
e5c8ee1
3638853
ec7810a
53585cd
1992123
db41f4c
0793638
94b066c
8be2e5d
34e3867
cbd5681
5963a8d
cd985c8
82f61d5
7882f3d
2a56add
5d3a268
v2.0.3
Compare Source
Bugfixes
<Form>
due to omitted 2nd generic toReact.forwardRef
. TypeScript users should use this version.Commits
e72db8a
8ed4418
428eff2
e2c9c04
bc9bc32
547dbed
v2.0.2
Compare Source
Bugfixes
useField
so that it returns a tupleCommits
edf4976
7b0752a
49254b8
42cc333
0517c8c
6b220c0
c16fbc4
v2.0.1
Compare Source
Formik 2 Migration Guide
Breaking Changes
Minimum Requirements
unknown
type, you must be on TypeScript 3.0 or higherresetForm
There is only one tiny breaking change in Formik 2.x. Luckily, it probably won't impact verry many people. Long story short, because we introduced
initialErrors
,initialTouched
,initialStatus
props,resetForm
's signature has changed. It now accepts the next initial state of Formik (instead of just the next initial values).v1
v2
What's New?
Checkboxes and Select multiple
Similarly to Angular, Vue, or Svelte, Formik 2 "fixes" React checkboxes and multi-selects with built-in array binding and boolean behavior. This was one of the most confusing things for people in Formik 1.x.
useField()
Just what you think, it's like
<Field>
, but with a hook. See docs for usage.useFormikContext()
A hook that is equivalent to
connect()
.<Field as>
<Field/>
now accepts a prop calledas
which will injectonChange
,onBlur
,value
etc. directly through to the component or string. This is useful for folks using Emotion or Styled components as they no longer need to clean upcomponent
's render props in a wrapped function.Misc
FormikContext
is now exportedvalidateOnMount?: boolean = false
initialErrors
,initialTouched
,initialStatus
have been addedgetFieldProps(nameOrProps)
There are two useful additions to
FormikProps
,getFieldProps
andgetFieldMeta
. These are Kent C. Dodds-esque prop getters that can be useful if you love prop drilling, are not using the context-based API's, or if you are building a customuseField
.getFieldMeta(name)
Given a name it will return an object:
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.