-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stories appearing in reverse order in v5.3.3 #9477
Comments
I think the problem has to do with this line in stable.inplace(stories, (s1, s2) => kindOrder[s1[1].kind] - kindOrder[s2[1].kind]); I'm not entirely sure what it does, but it seems to sort the stories by their category, but amongst themselves. This process must inadvertently reverse the original order of the stories themselves? This appears to be something new @shilman added two days ago in #9424 (to fix #9419). Maybe you can chime in? |
Thanks for the issue @benmvp, can you just clarify with a screenshot -- is it the stories are the wrong order within a kind? Or are the kinds in the wrong order? Or both? |
@tmeasday thanks for the quick reply! It appears like both. The kinds used to be sorted alphabetically, and now they are backwards. The stories w/in the kind used to be sorted by their |
Thanks @benmvp and @chris-pearce. Fix coming. |
¡Ay Caramba!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.3.4 containing PR #9482 that references this issue. Upgrade today to try it out! Closing this issue. Please re-open if you think there's still more to do. |
Yup, that fixed it! Thanks! 🎉 |
Describe the bug
I upgraded from 5.3.2 to 5.3.3 today and my stories were displaying in reverse order than how they are exported (using CSF).
To Reproduce
Expected behavior
I would expect that the stories would be in the order that they were exported in, which is how they worked in 5.3.2.
System:
Additional context
One thing to note is that if I force the sort order following the sorting stories guide, they appear in alphabetical order.
The text was updated successfully, but these errors were encountered: