John Rom

@ops1ops sorry I misspoke, it doesn't set touched until after the field is blurred. This is the default behavior in many forms so that the user is not presented with...

@ops1ops that's a slightly different topic than this issue, feel free to open a separate issue or join the discord to ask your question. if you open an issue please...

@JaredDahlke it's definitely understandable that this is a pretty severe limitation for some large datasets. the problem with solving it by validating only one field at a time, is that...

@jesseko I don't know if Yup supports that, sorry (I don't use it). The important determinations for making this change a reality are: ### An Opt-In method We need to...

In v3, useFormikContext doesn't contain state, so the equivalent would be `useFieldMeta()`, but you cannot randomly add hooks depending on props, so that needs to itself be a prop like...

Most major performance issues are resolved in my v3 umbrella PR. Unfortunately it was never released by the maintainer. A separate renderer will be required for useTransition. I have a...

I haven't actually found any tradeoffs in my PR or run into any major issues. I would probably recommend trying it out. UseTransition will be great in concurrent mode but...

I also have a PR for strong types over v3.

I don't foresee concurrency being something everyone will be able to dive into in a meaningful way without the entire React community getting used to it. Kind of like adopting...

I would personally fight against the desire to gut Formik and rewrite it for concurrency. The only way I would implement something like this is if it can be implemented...