John Rom

This is done and works just as it did before (no splitting) using the "react-native" field in package.json. I just don't use React Native so I don't know whether that...

@kuzaxak this PR is complete as far as I know. I requested Formik release it as an official RC so it can get more testing done, but there has been...

Feel free to test my RC via npm with `@johnrom/[email protected]` in order to test and add any issues you may find here, with the following caveats: - I will not...

I updated my previous comment to use the correct PR for the documentation. The previous one was the wrong branch. The new PR is here: https://github.com/johnrom/formik/pull/11

@adam-thomas-privitar you don't have to use the micro-hooks, you can use `useFormikContext().setFieldValue`. The micro-hooks are from the original v3 PR Jared created which optimized the hooks a different way. This...

The module issue should be fixed in `3.0.0-rc2`. With the updated `module`, you can do this after node modules are installed: ```tsx import { useField } from '@johnrom/formik-v3'; const MyField...

@Tigge depending on whether the Formik Plugin API is adopted and we move Yup there, #3109 would probably be the time we examine prepareDataForValidation. I'm definitely not involved with the...

As mentioned before, this isn't the relevant issue and I'm not involved in the matter, so I have no comment on your response above. I personally would rather that discussion...

A quick (lol not quick) recap of the purpose and benefits of this Umbrella set of changes which I am recommending for v3: ### 1. Exposes "future state" You can...

@keremciu whether my changes are ever merged into Formik itself isn't up to me, but my fork is available for test purposes here: https://www.npmjs.com/package/@johnrom/formik-v3 It has 1-6 above and Strongly...