-
|
I'm wondering why the example Components (button, header, page) in the svelte CSF version have the CSS in external files, not in the svelte file? Is that unusual pattern required by storybook for correct rendering? Or is it just hang over from when converting examples from another framework. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
I think the examples must have changed as though I have Confused! :D |
Beta Was this translation helpful? Give feedback.
-
|
@JReinhold I wonder if you can shed any light on this? No worries if you are to busy as I can wait for the new release. |
Beta Was this translation helpful? Give feedback.
-
|
The example stories you get on init try to be as framework agnostic as possible, which is why they have separate CSS. you don't have to do that with Storybook, you can build your components however you like. The examples don't come from the addon repo, but from the core repo, which is why you're seeing this difference. Example stories on init showcase some basic Storybook understanding, while examples from the addon showcase the Svelte CSF specific syntaxes. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I wondered if something like that but couldn't trace. As long as not indicating restrictions! Been playing with next.23 and it's good. One weird typescript error when I import a decorator but all working really well. Also spotted a couple of doc errors but will wait for publish. |
Beta Was this translation helpful? Give feedback.
The example stories you get on init try to be as framework agnostic as possible, which is why they have separate CSS. you don't have to do that with Storybook, you can build your components however you like.
The examples don't come from the addon repo, but from the core repo, which is why you're seeing this difference. Example stories on init showcase some basic Storybook understanding, while examples from the addon showcase the Svelte CSF specific syntaxes.