Yeah it was easier I guess your way rather than using const Transition = React.forwardRef(function Transition(props, ref) {
return ;}); to make the fix (for material ui's back to top example) which I think would have worked because findDomNode is deprecated but after using a forward ref the error did disappear on other elements. Material UI i think is slowly fixing this or at least showing how to fix in docs but some things still show that annoying error so you have to put forward ref on a bunch of things. Beats shutting off strict mode though.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome. That is great to hear
Yeah it was easier I guess your way rather than using const Transition = React.forwardRef(function Transition(props, ref) {
return ;}); to make the fix (for material ui's back to top example) which I think would have worked because findDomNode is deprecated but after using a forward ref the error did disappear on other elements. Material UI i think is slowly fixing this or at least showing how to fix in docs but some things still show that annoying error so you have to put forward ref on a bunch of things. Beats shutting off strict mode though.