Supports for tags in <Meta/>

[j3rem1e]

Storybook v7 supports tag on the meta property. However, tags should be set on the story indexer to be seen by the autodocs feature. The only tag used today by storybook is autodocsAFAIK.

This PR add supports for tags and an alias to a 'autodocs' property. Tags can only be specified as a static property, because it should be build by parsing the AST.

Examples:

<Meta title="XX" autodocs/>

<Meta title="XX" tags="autodocs"/>

<Meta title="XX" tags={['autodocs', 'a', 'b']}/>

[benmccann]

Cool! Just FYI, @JReinhold had another idea regarding Meta as well: #135

[j3rem1e]

@JReinhold are you Ok with theses changes ? thanks !

[benmccann]

Awesome! This is exciting!

[benmccann]

@j3rem1e just a quick heads up that there's a merge conflict

[j3rem1e]

It should be good now. And I included your changes

[shilman]

🚀 PR was released in v4.0.7 🚀

[shilman]

🚀 PR was released in v4.0.7 🚀

[shilman]

🚀 PR was released in v4.0.7 🚀

[nickgroenewegen]

I'm not sure if this is the correct place to mention this but since this PR was released only a few days ago i am hoping this would get noticed.

Using the express meta as JS results in a error: 'TypeError: Cannot read properties of undefined (reading 'DefaultExample')'

Eg:

<script content="module">
	import { Story } from '@storybook/addon-svelte-csf';
	import Example from './example.svelte'

	export const meta = {
		title: 'Components/Example',
		component: Example
	}
</script>

<Story name="Default example">
	<Example />
</Story>

When using the depreated <Meta /> everything works as expected. Eg:

<script content="module">
	import { Story, Meta } from '@storybook/addon-svelte-csf';
	import Example from './example.svelte'
</script>

<Meta component={Example} title="Components/Example" />

<Story name="Default example">
	<Example />
</Story>

This happens right after a clean install of a sveltekit app. A repository that showcases this can be found here

I'm not sure if this is a mismatch in configuration or a possible bug?

[j3rem1e]

Thanks for reporting it. I'll check that.

[j3rem1e]

@nickgroenewegen

It's a typo on the documentation. It's not <script content="module">. but <script context="module">.

[nickgroenewegen]

@j3rem1e Ah yes. I literally took over what was on the documentation and did not notice it :), thanks for pointing it out!