-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Formik v3 Umbrella PR. #3231
base: main
Are you sure you want to change the base?
Formik v3 Umbrella PR. #3231
Conversation
Added Ref State. Added useSelectorComparer. Starting to build subscriptions.
use-subscriptions might not work in React 17? Seems returning the previous value doesn't bail out the render.
Sync up formik-native and formik for v3.
…te will do. If we call our own reducer then use useReducer dispatch, `state.values !== getState().values`.
…ormikReducerState + FormikComputedState. Add Fixtures and Tutorial code to /app.
Consolidate State and Add Tutorial + Fixtures.
For some reason, the tests for remove only worked when they were async or render was moved from beforeEach to the individual tests.
Add missing useIsValidating hook
Hi, do you have any plans with that v3 version? Or maybe you need some help? We would like to use v3 in our application and try to figure out what is the best way to do so. |
@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 no movement there. Unfortunately I'm fully loaded up on client work at the moment, so I haven't decided where to go next. |
Would love to see the RC published! I have a decent size monorepo that I can help test things on and give feedback on perf and such. |
I see that you published it as rc under your own npm package, can we use it? Or we need to use git dependency? |
Feel free to test my RC via npm with
|
This is totally understandable :) If we will find some problems we always can fork your fork and propose a change. |
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: johnrom#11 |
@jaredpalmer Is there any plan to move this forward? It seems like from the original Todo's, only the documentation remains to be complete. Thanks for your time! |
@johnrom Just letting you know the published Im having trouble using this in place of my existing installation, since |
@adam-thomas-privitar you don't have to use the micro-hooks, you can use The micro-hooks are from the original v3 PR Jared created which optimized the hooks a different way. This one instead removes state from useFormikContext which makes it a stable hook which will not trigger re-renders. I'll take a look at the |
The module issue should be fixed in With the updated import { useField } from '@johnrom/formik-v3';
const MyField = (props) => {
const [field] = useField(props);
return <input {...field} />;
} |
Yeh I suspected as much! Sadly...Im based on the v3 beta and so have a fair amount of code on top of the "new" hooks. I will need to do a bit more refactoring. Thanks for fixing the |
… handled anyway. We'd want to dispatch a request to validate specific fields which can be cancelled as more validations are requested.
This pull request is being automatically deployed with Vercel (learn more). formik-docs – ./🔍 Inspect: https://vercel.com/jared/formik-docs/2LvHDxC73yoFJbQhSLohVRBq3oDr |
@quantizor, noticed you approved a PR for a release that went out a few days ago. This might be great to consider approving, as I've run into #3335 myself! I'm happy to make any changes necessary to resolve any merge conflicts. |
closes #3099
Todo: