Adam Thomas

It looks like its fixed in Safari 14.1.1.

@johnrom Yeh I'm familiar with your PR! Its a real shame it didn't get merged. I think youd get a lot of traction for a proper community fork of this...

(my second main issue with formik is no type safety on dot notation paths which can be solved with typescript template literals -- but i digress) https://www.typescriptlang.org/play/?ts=4.1.0-pr-40336-88

Could it be better to dump the refs entirely and go all in on concurrency? Im tempted to just give it a go on Formik 3 beta as it seems...

(I guess it would turn any listening component tree to a concurrent one -- but I think it wouldnt be a bad thing. But like you, I'm not well versed...

Hmm yeh. I guess what I proposed is a technically breaking change -- but React release notes state: > In our testing, we’ve upgraded thousands of components to React 18....

Yeh I don't necessarily disagree. I'm looking for a cheap and dirty solution to my problems short-term, and suspect I'm not alone. Any fork I'd produce would exist only to...

Cool! Yeh I'll check it out. I'd probably lean on the non-types one first before inevitably attempting the typed version and realising how many issues we have 😛. At the...

I just wanted to update on my findings. I spent some time doing a horrendous hack that essentially did something like this: * Wrapped all of the return values of...

> I think in a library of controlled inputs like formik, the only real use case for useTransition is for effects after the onChange, because like mentioned above the very...