How to restore the behavior of v3 in v4? about use-debounce

[ivan-aksamentov]

Okay, you just witnessed a rubber duck debugging session. 🦆

I investigated the

throws errors for all form fields in the form

part and found that I should not have returned from the .then() part of the snippet above, because formik treats the returned things as errors (I returned valid values). So, this was a bug (also, "thanks" to eslint promise/always-return rule that convinced me I should return something). It seems that previously the returned thing did not reach formik, hiding the bug, but now it does reach somehow.

So the question is: what changed in use-debounce from v3? Did it not return the value before and now it does?

Anyways, this solves it for me, so feel free to close. But I hope this information might help someone else to debug their transition to v4.

[ivan-aksamentov]

@tryggvigy, small planet :)

hope covid19_scenarios is going well

Yep, it's thriving. 6+ months into pandemic, we are now swimming in data. Initial predictions were totally correct too. Not sure if I should be glad or sad about it all. Just released changes for "The Second Wave". Not looking good.

Feel free to close this, folks. Might also add a quick note on the new return behavior to the list of breaking changes, and/or to the readme, in case someone else steps on it.

[xnimorz]

I'll add it to the changelog and then I'll close the issue :)

[tryggvigy]

Hi @ivan-aksamentov! Nice to see you again 😄 hope covid19_scenarios is going well.

So the question is: what changed in use-debounce from v3? Did it not return the value before and now it does?

Yes, that's right. The new version mimics lodash's implementation of debounce which returns the value.
I'm sorry you had to spend time debugging!

[xnimorz]

Hi @ivan-aksamentov

Yes, now v4 use-debounce returns the value.

[xnimorz]

Added f9f4cb3 :)