add validationSchema to FormikContext

[ldicocco]

useFormikContext doesn't return validationSchema, although the type says it should do and the connectin v1 did.
This PR fixes the problem and adds a specific test for this case.

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/jared/formik-docs/1dgk3anhx
✅ Preview: https://formik-docs-git-fork-ldicocco-bugfix-useformikcontext-72fb91.jared.now.sh

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e5a3cc3:

Sandbox	Source
Formik TypeScript Playground	Configuration

[josejulio]

Also hitting the same issue, if anything is needed to help, please let me know.

[desfero]

@ldicocco also it probably worth to add validate the same way you did with validationSchema because if you look at types

export declare type FormikContextType<Values> = FormikProps<Values> & Pick<FormikConfig<Values>, 'validate' | 'validationSchema'>;

you can see that both validate and validationSchema are picked.

@ldicocco @josejulio is there any workaround to get validationSchema?

@jaredpalmer is it possible to merge this one and release as otherwise formik is broken in case someone is using yup metadata to get the desired UI

[SamKirkland]

This was actually a breaking change in v2.
I'm updating from v1.5.8 which used to provide validationSchema in <FormikConsumer>

Example 1 - change the imported formik version to v2.1 or above and validationSchema will no longer be in context
Example 2

[egoreburial]

cmon please merge it! There is no chance to dynamically check if come field is required or not and render it to UI !!!

[Maxim-Chugaev]

please merge it !

[Maxim-Chugaev]

@josejulio What about workaround ?

[johnrom]

Some small changes requested.

Testing useFormikContext may need further thought, unless it is acceptable to test props.

[johnrom]

add this to formikBag itself

[johnrom]

is it proper to put tests inside of components? I've never tried it. The normal formik renderer in the rest of the tests exposes the props to the test runner via a special API, like this:

        const validate = jest.fn(() => Promise.resolve({}));
        const validationSchema = {
          validate,
        };
        const { getProps } = renderFormik({
          validationSchema,
        });

        expect(getProps().validationSchema).toBe(validationSchema);

I don't see any tests using useFormikContext though. Maybe this is something we need to add? Or is validationSchema being passed via Formikbag enough proof that it's working?

[johnrom]

is string valid for validation schema? thought it had to be a Yup object. Other tests use { validate: jest.fn(() => Promise.resolve()) }.

[josejulio]

@josejulio What about workaround ?

I used the validation schema that I knew was in place directly.

[IevaDrauge]

Can someone please merge/fix this? It is a very crucial missing feature right now...

[raphaelpc]

Hello! Any news on this? Thanks!

[sudo-vaibhav]

This is a very important feature, I hope it gets merged soon.