You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you very much for the nice package, which has already saved us a considerable amount of time.
Currently, shouldComponentUpdate() seems to return true only when the navs change. This messes with my workflow in multiple ways:
I want to disable the form as it is being submitted;
My form has children (a custom button which animates while the form is being submitted, a "Saved!" message when the data the form is currently displaying is stored server-side, etc.).
To experiment, I overrode shouldComponentUpdate() and made it always return true. However, this made my form's fields lose focus on change arbitrarily. This leads me to believe the author is using shouldComponentUpdate() to prevent this buggy behaviour as opposed to solely as a performance optimization.
Hello,
First of all, thank you very much for the nice package, which has already saved us a considerable amount of time.
Currently,
shouldComponentUpdate()
seems to returntrue
only when the navs change. This messes with my workflow in multiple ways:To experiment, I overrode
shouldComponentUpdate()
and made it always returntrue
. However, this made my form's fields lose focus on change arbitrarily. This leads me to believe the author is usingshouldComponentUpdate()
to prevent this buggy behaviour as opposed to solely as a performance optimization.Here's an SSCCE: https://codesandbox.io/s/q8o8mmlyoj
Thanks for any help you may be able to provide. I might start work on a PR in parallel.
The text was updated successfully, but these errors were encountered: