John Rom

> Just to be clear, the value designed for this is the PulishedUtc of the first published version. Specifying a publish date isn't the most common thing in the world,...

There hasn't been any movement on supporting Maps or Sets, though the last comments on the original issue #1339 say that they might add support upstream sometime soon. I don't...

It seems like in most cases, the Form Fields aren't being wrapped in a FormikProvider (like ``) when testing. @Badyanchik validateField is kind of interesting. Basically, you'd still need to...

`Formik` component or another `FormikContext` provider must appear above your `useField` hook or `Field` component in the component hierarchy, even when testing. If you're using `useField`, you don't need `Field`,...

@jvitorr did you try https://github.com/jaredpalmer/formik/issues/2291#issuecomment-619577563 ?

Just my 10 cents, I'm a bit mixed on this one. On the one hand, I think the `FormikErrors` object should be treated as a 1-1 mapping of errors to...

@defunctzombie I view the `render` method as being somewhat deprecated, but you can pass props from the parent to either the render or child components. If you're breaking things out...

I think mixing field errors and form errors is less graceful since form-level errors are often API or app-level errors whereas field errors are generally fixable user errors. I think...

We don't actually have any mechanism for telling Formik whether a submit was successful, only if validation was successful, so this submittedCount wouldn't really have the meaning that is intended....

> In order to make initialValues update after submit I would have to turn them into component state, even though they are not state. They are state, if you need...