Closed MarkDGithub closed 2 years ago
PR is welcome. BTW, can give an example to demonstrate this problem?
can give an example to demonstrate this problem?
I recreated and simplified the problem here . The stale counter is just a simplification. This is where I update the Redux store in my real application. PR: #10
I see. I checked out you branch, it seems has some issues with the drag demo
it seems has some issues with the drag demo
I can't reproduce this issue, I'm using respectively the following commands: yarn install, yarn build-storybook, yarn storybook
I also tried if the problem occurs after cloning the project again and checking out the new branch (so basically a blank sheet). But the problem still doesn't occur.
I figured it out. It was caused by one of my chrome extensions.
Thanks for accepting. Will the npm package be updated automatically?
I just published it to npm. try toreinstall the package
Hi, I appreciate the work you have done with this project and I would like to ask if I could help you with the library. One of the issues which I found is that the event handlers use a stale React state. I know that there is a workaround by using useRef(). However, this gets complicated when using Redux and leads to duplicate data. I solved this for the events by refactoring the code to React hooks. Meanwhile I also updated the npm dependancies. You can find my changes here: npm-updates-and-using-react-hooks I could create a pull request.