storybookjs/storybook

Automigration: Clean up features object

Open

#19,732 opened on Nov 2, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (89,909 stars) (10,058 forks)batch import
clifeature requesthelp wanted

Description

  • Remove main.js features that have been removed if it doesn't change the behavior
  • Warn about features that have been removed if it's a breaking change

Contributor guide

Tech stack
typescriptjavascriptnodejs
Domain
developer experiencetooling
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Storybook configurationUnderstanding of automigration concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the automigration code in Storybook, likely in the 'lib/core server' or 'automigration' directory. Look at existing migration functions that handle 'features' in main.js. The issue asks to remove features that have been removed without changing behavior and warn for breaking changes. Check linked PRs or comments for guidance, but currently none exist.