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
Awesome lib, I've been using it for a couple of years!
You've probably heard about the upcoming Concurrent Mode, which imposes some additional restrictions to the components. It seems that react-barcode is not fully compatible because of a string ref begin used. Here is a warning I'm seeing after wrapping <Barcode> into <React.StrictMode>:
Warning: A string ref, "renderElement", has been found within a strict mode tree.
String refs are a source of potential bugs and should be avoided. We recommend
using useRef() or createRef() instead. Learn more about using refs safely here:
https://fb.me/react-strict-mode-string-ref
The text was updated successfully, but these errors were encountered:
Why you don't publish this changes ? there is pr merged to master month ago and in 1.4.1 i still get this strict mode message....
When are you planning to do this ?
👋 @kciter,
Awesome lib, I've been using it for a couple of years!
You've probably heard about the upcoming Concurrent Mode, which imposes some additional restrictions to the components. It seems that
react-barcode
is not fully compatible because of a string ref begin used. Here is a warning I'm seeing after wrapping<Barcode>
into<React.StrictMode>
:The text was updated successfully, but these errors were encountered: