context-based comps, hooks and missing provider in 2.0

[slorber]

Hi,

Currently, it's possible to use formik in v2 which does not require a parent FormikProvider

But this will make all components using FormikContex to fail. It's actually a bit nasty because there's no warning on mount, but as the context methods are not injected into the consumer components, we get this kind of errors:

I think we should

1) Make it fail fast

const form = useFormik()
return <FieldArray>...</FieldArray>

This should crash/error on mount instead of on attempt to modify form

2) Document that this is possible:

const form = useFormik()
return <FormikProvider value={form}><FieldArray>...</FieldArray></FormikProvider>

It's a workaround I'll use temporarily (as I'm for strong typesafety/manual typesafe wiring, I try to avoid using context-based components)

3) Allow all context-based components to be able to receive the form as props

const form = useFormik()
return <FieldArray form={form}>...</FieldArray>

[jaredpalmer]

All context based components and hooks should crash with a warning. In a perfect world there is a formik.getFieldArrayHelpers that can be used without context just like formik.getFieldProps

[maddhruv]

Closing due to long inactivity