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
Since upgrading to Storybook 8 (web components + Vite), when I view the code in the AutoDocs page, the tags are escaped (they were not in Storybook 7). It also shows a ton of whitespace (which has always been an issue).
Is there a way to clean this up, e.g., using Prettier, to be consistent with the HTML Addon? It's odd that Storybook has this functionality built in but I need a third-party plugin for the addon panel and the two views differ significantly.
Here's code for a simple button story (it's also showing the decorator-specified wrapping tag, which I would rather not):
I'm building components in Stencil JS 4.13, but I don't see this behavior in your storybook.new environments (tried HTML and Lit). I can update with a link to my actual repo once committed.
I have the same problem on Storybook 7.6.17 and 7.5.3 so I guess it's not related to 8.0 version, on the other hand, lit render works but it causes double calls to constructor of components.
Describe the bug
Since upgrading to Storybook 8 (web components + Vite), when I view the code in the AutoDocs page, the tags are escaped (they were not in Storybook 7). It also shows a ton of whitespace (which has always been an issue).
Is there a way to clean this up, e.g., using Prettier, to be consistent with the HTML Addon? It's odd that Storybook has this functionality built in but I need a third-party plugin for the addon panel and the two views differ significantly.
Here's code for a simple button story (it's also showing the decorator-specified wrapping tag, which I would rather not):
To Reproduce
I'm building components in Stencil JS 4.13, but I don't see this behavior in your storybook.new environments (tried HTML and Lit). I can update with a link to my actual repo once committed.
System
Additional context
No response
The text was updated successfully, but these errors were encountered: