Upgrade Storybook #1459
Merged
Upgrade Storybook #1459
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://github.com/storybookjs/storybook/releases from v7.0.5 to v7.1.1. There's a v7.0.27, so I recommend skipping the release notes, except maybe for https://github.com/storybookjs/storybook/releases/tag/v7.1.0 and https://github.com/storybookjs/storybook/releases/tag/v7.0.25.
The latter patch release fixed an issue that prevented us from rendering
VisCanvasin decorators. I demonstrate this inAnnotation.stories.tsxto avoid duplication, but that's the only place I found this pattern to be really useful. At first, I wanted to use it in theHeatmapMesh.stories.tsx, for instance, as a way to avoid declaring a customrenderfunction in theDefaultstories (and, as a consequence, avoid spreading theDefaultobject in all the subsequent stories objects), but on second thought, it doesn't save much code and I find the current version more explicit.Anyway, at least we know it's doable now.