John Rom

An effect is the only way to accomplish this in Formik currently

You're free to open a PR with the features requested here. I agree if there's no Form level validation, there's no reason to run all validations. However, it's possible that...

Definitely not stale, but `keyof` implementations are _extremely broken_. This needs to support nested fields. See work at https://github.com/johnrom/formik-typed for example of a workaround. Combined with extending #1336 to all...

The Field component doesn't work in React Native, you'll instead need to connect the `Input` or `TextInput` components to Formik's API using `handleChange`, etc. https://formik.org/docs/guides/react-native (I have plans for this...)

If I'm not mistaken (I don't have Formik in front of me) you can do something like: ```tsx import { getIn, useFormikContext, FieldHookConfig, Formik, FieldArray } from 'formik'; const MyNativeField...

Doing a little cheating makes this possible. I didn't test too thoroughly, but it seems to work. The main issue is that I had to override the type inference (with...

Basically, a `Formik` contributor could change the types incorrectly. I wish we could [ignore a specific rule](https://github.com/Microsoft/TypeScript/issues/19139) so we wouldn't have to use `as` and we could protect against all...

I imagine the @type being a OneOrMany, that change would have to be applied everywhere, but deserialization should still attempt to find a best common denominator of all the types...

checking in to see if this is on anyone's radar. found the plugin very useful, but we have some images we'd like to transition between on mobile.

@lemoinem I would still open a new issue for the above. This issue is specifically related to specifying a literal string value (to support my implementation of a discriminated union,...