-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Add Addon migration guide for Storybook 7.0 page #21932
Conversation
@ndelangen — I noticed this sentence in the full migration notes:
I opted not to include that here. My thinking is that if they're making the code changes to accommodate that breaking change, we might as well point them only to the new packages and not to an already-deprecated technique. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good for @ndelangen to review too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Michael Shilman <shilman@users.noreply.github.com>
Here is what I did for addon-notes support in storybook 7, I added this custom panel to the manager.js file:
|
What I did
/docs/addons/addon-migration-guide
How to test
Follow the documentation contribution instructions for this branch,
addon-migration-docs
.Checklist
MIGRATION.MD
Maintainers
make sure to add the
ci:merged
orci:daily
GH label to it.["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]