storybookjs
React Native: Endless story switching loop when notes are open
When you start react-native-server, open notes tab and select a different story, storybook starts switching between old and new story back and forth.
If you have canvas open it does not happen.
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
The combination of this issue + lack of fast reloading support + random warnings about duplicate ids has rendered storybook pretty much useless on react native for us - for months now.
@mtford90, what exactly are you trying to achieve with this comment? If an open source tool is broken and it doesn't work well enough for you you can always fix it yourself. There are plans that we have to make storybook better but I cannot simply work on it whenever I want to. I have plenty of things to do at my work, when I get back home I want to rest instead of working on another serious project. I will get back to it when I will finally have a chance.
Just do not feel entitled to anything in open source.
@mtford90, what exactly are you trying to achieve with this comment?
@Gongreg it wasn't meant as a personal attack - apologies if it came across that way. As far as what I was trying to achieve: informing the maintainers that the accumulation of RN issues has rendered it essentially broken and that it has been that way for quite a long time.
you you can always fix it yourself.
I may well make an attempt at this.
@mtford90, thank you for clarifying the message. I agree that RN Storybook is in a hard place. For me now the first priority is to set up e2e tests and fix existing issues like broken fast refresh.
As the project stands right now (no tests), we cannot keep it not broken, since a lot of internal dependencies are keeping updated.
Also if you have any questions always feel free to ask, I would gladly help. It is a lot easier to help with issues than to actually find time to develop.