-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Bug]: 7.0.0-rc.9 Decorators are broken in custom render components #21900
Comments
There was an intentional breaking change to how we treat decorators in docs in Can you try setting |
@shilman you're right, if I change that parameter it starts to work again. I've updated my reproduction to show it both ways. |
Yee-haw!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.1.0-alpha.0 containing PR #21902 that references this issue. Upgrade today to the
|
Seems to be related to the MR. The |
@StraightOuttaCrompton yes that change has been reverted by the PR that closed this issue. It has not yet been released to 7.0, but there is a 7.1 alpha version that includes it. @shilman it looks like the table of contents was not updated in your PR, though, which gives a dead link as noticed above. |
Good catch @IanVS -- fixed I'll patch this back to 7.0 in 10h or so unless issues are raised against the prerelrease in the meantime. |
Son of a gun!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.3 containing PR #21902 that references this issue. Upgrade today to the
|
Describe the bug
I started to get an error indicating that my react-router decorator was no longer working when I upgraded from rc.5 to 7.0.2. I narrowed it down to starting in rc.9, and have reproduced the issue in a stackblitz, linked below. It seems like decorators are no longer used in some situations, depending on whether arguments are provided to a custom render function.
To Reproduce
https://stackblitz.com/edit/github-ytdmum?file=src%2Fstories%2FPage.stories.tsx&preset=node
System
Additional context
No response
The text was updated successfully, but these errors were encountered: