Problem
Stories can define initial params using arbitrary (unsafe) string keys.
When the structure of a component’s form changes (e.g. param definitions are renamed or removed), these initial params may become unlinked — meaning they are no longer recognized or used by the component.
Currently, there’s no way to diagnose or visualize this mismatch.
Proposal / Solution
-
During story build:
- Call the story’s builder once and collect all registered params.
- Compare them against the initial params defined in the story.
- If any initial param key was not registered, mark the story as having unlinked params.
-
In the UI:
- Display a warning icon next to the story.
- Provide a tooltip or dialog explaining that some initial params are unused because their keys no longer match the component definition.
Acceptance Criteria
Problem
Stories can define initial params using arbitrary (unsafe) string keys.
When the structure of a component’s form changes (e.g. param definitions are renamed or removed), these initial params may become unlinked — meaning they are no longer recognized or used by the component.
Currently, there’s no way to diagnose or visualize this mismatch.
Proposal / Solution
During story build:
In the UI:
Acceptance Criteria