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
Group name includes leading and trailing whitespace #13311
Comments
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! |
Hey, can you tell me how to do that? I tried running |
@x4th You probably need to run with |
I have the exact same issue with storybook v6.2.9. |
@bodograumann Can you give an example of such a story file? |
At least it is consistent, so that when I include the trailing space in the sort order, it works. :-D
I left away the other two stories for brevity. Relevant
|
@bodograumann Thanks. I confirmed an fixed the problem: #15038 |
Olé!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.3.0-beta.1 containing PR #15038 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Just upgraded to 6.3-rc.11 and it works very well. Thank you! |
I'm trying to move one component group to the top to have it displayed before all others.
This however has no effect and when I looked inside the related story I see I used:
If I change
order: ['Line Items'],
toorder: ['Line Items '],
in the first file ortitle: 'Line Items / Single Line Item',
totitle: 'Line Items/Single Line Item',
the group moves to the top. If there's a reason why whitespace here should matter you should at least make a note in the docs warning users to not have spaces around the slash.The text was updated successfully, but these errors were encountered: