Releases: jaredpalmer/formik
formik@2.2.3
formik-native@2.1.11
Patch Changes
-
e0a28e6
#2867 Thanks @umidbekkarimov! - Fix low priority validation for browser password autofill. -
Updated dependencies [
e0a28e6
,958d67c
]:- formik@2.2.3
formik@3.0.0-next.2
formik-native@2.1.10-next.2
Patch Changes
-
e0a28e6
#2867 Thanks @umidbekkarimov! - Fix low priority validation for browser password autofill. -
Updated dependencies [
e0a28e6
,958d67c
]:- formik@3.0.0-next.2
formik@2.2.2
Patch Changes
00f95ec
#2854 Thanks @umidbekkarimov! - Fix low priority validation race condition.
formik-native@2.1.10
Patch Changes
-
00f95ec
#2854 Thanks @umidbekkarimov! - Fix low priority validation race condition. -
Updated dependencies [
00f95ec
]:- formik@2.2.2
formik@3.0.0-next.1
Patch Changes
1c2175a
#2848 Thanks @jaredpalmer! - Ensure that parse and format aren't passed through in Field components
formik@3.0.0-next.0
Major Changes
-
5efd691
#2255 Thanks @jaredpalmer! - Addedparse
,format
, andformatOnBlur
togetFieldProps
options,<Field>
, anduseField
. Going forward, there is no reason aside from backwards compatibility to continue using eitherformikProps.handleChange
orformikProps.handleBlur
. These are both inferior to theonChange
andonBlur
functions returned bygetFieldProps()
which the ability to utilizeparse
,format
, andformatOnBlur
.Breaking Change
Instead of just passing backformikProps.handleChange
andformikProps.handleBlur
, theonChange
andonBlur
handlers returned bygetFieldProps()
(and thususeField
/<Field>
) are now scoped to the field already and now accept either a React Synthetic event or a value. In the past, you could need to curry the handler with the string name of field to get this functionality. This likely doesn't impact many users, but it is technically breaking nonetheless.
formik-native@2.1.10-next.1
Patch Changes
- Updated dependencies [
1c2175a
]:- formik@3.0.0-next.1
formik-native@2.1.10-next.0
Patch Changes
- Updated dependencies [
5efd691
]:- formik@3.0.0-next.0