Erick Katzenstein
Erick Katzenstein
I'd turn the magnifying glass the the other way. The letter "Q" carries a lot of weight these days
Another workaround is turn off "strict mode" for React.
Yes, this is still an issue.
I had this issue appear out of nowhere and have been unable to resolve it.
I was experimenting with `react-three-renderer-fiber` and this may have interfered somehow. After removing it as a dependency (and running a fresh clone of my repo), it worked. Still a mystery...
@toxicFork I'm unfortunately going to have to stop using this library if a React 16 update doesn't happen soon. There are other libraries (like material-ui) that now only work with...
Here is what I'm using meanwhile as a workaround. @toxicFork Am happy to submit a PR if you think it's worthwhile. ``` const uniforms = { woodTexture: { type: 't',...
Just to be clear, this is not fixed. You haven't submitted a PR to fix it. A pending PR is here: https://github.com/hlashbrooke/Code-Snippet-Library/pull/8/files
It's not completed. There is specifically a "key" property that doesn't work. One can use setMessages in useEffect, but that's completely unrelated to this issue. It is not a workaround.
Still experiencing this issue with 10.16.4