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
So the args state is set once to storyContext.args and then never set again, except via the events.
When you change args, the events are fired, so that works.
When you change story (to a different component) a whole new docs container is rendered, so a new ArgsTable is re-created, so that works.
When you HMR the story, there are no events or recreation, so we don't pick it up.
I'm not quite sure what the best solution is. Here are some quick thoughts:
a) We could emit an event when the implementation of a story changes (i.e. HMR), and pick that up here.
b) We could take steps to ensure the args table (or entire docs container) is recreated on HMR.
c) We could add some kind of key to the docs context that changes whenever HMR happens
Repro. In any args story:
The text was updated successfully, but these errors were encountered: