You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Storybook has a policy of deprecating APIs with util-deprecate to give users advanced notice of their removal. Now in 6.0 we should remove most of those deprecations and clean up the code.
What
Scour the code for util-deprecate:
If we think a deprecation is "too recent" or removing it will be too disruptive to users, add to a list of "remaining deprecations" in the PR description for review. Otherwise, remove/change API & clean code.
Update docs & MIGRATION.md for each change
The text was updated successfully, but these errors were encountered:
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!
Why
Storybook has a policy of deprecating APIs with
util-deprecate
to give users advanced notice of their removal. Now in 6.0 we should remove most of those deprecations and clean up the code.What
Scour the code for
util-deprecate
:The text was updated successfully, but these errors were encountered: