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
{{ message }}
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.
This issue also applies when using the Docs addon (as it's a single page), meaning that all of the components within the page have the props of the first created component.
From what I can see, the values for the first component are stored against prop names when the page is navigated to and then the same values are used for every value for each component following. Could we try assigning the values to a unique property of each element instead?
Thanks!
The text was updated successfully, but these errors were encountered:
Same problem. As soon as I tricked smart-knobs into supporting my component it ruined my docs page. I'd be happy at least with it being disable for docs page examples where the Knobs panel is not available as a start.
bastienrobert
added a commit
to unlikelystudio/addon-smart-knobs
that referenced
this issue
Mar 20, 2020
Code:
Button.stories.tsx
Expected Result:
Actual Result:
This issue also applies when using the Docs addon (as it's a single page), meaning that all of the components within the page have the props of the first created component.
From what I can see, the values for the first component are stored against prop names when the page is navigated to and then the same values are used for every value for each component following. Could we try assigning the values to a unique property of each element instead?
Thanks!
The text was updated successfully, but these errors were encountered: