-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extractArgTypes
doesn't function for @storybook/html
since v6.5.0
#18376
Comments
I'm happy to jump on fixing this myself if someone could point me in the right direction. |
Thanks, @shilman for taking care of this. |
Jeepers creepers!! I just released https://github.com/storybookjs/storybook/releases/tag/v7.0.0-alpha.18 containing PR #18831 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Gadzooks!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.10-alpha.1 containing PR #18831 that references this issue. Upgrade today to the
|
@shilman I just gave it a try and can confirm that the issue is fixed. Thanks a lot for taking care of this. 🙏 |
Yippee!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.10 containing PR #18831 that references this issue. Upgrade today to the
|
Describe the bug
Up until v6.4.22 of Storybook, we've been able to enhance the argTypes hooking into the
docs
parameters viaextractArgTypes
. While this hook seems to still work for@storybook/web-components
for versions6.5.*
it suddenly stopped calling the function for@storybook/html
of6.5.*
versions.To Reproduce
I've created a repository with
README.md
instructions to reproduce the error.https://github.com/weaintplastic/storybook-html-extractArgTypes
System
Additional context
We are using
@storybook/html
in combination withenhanceArgTypes
to render web components with StencilJS in stories and enhance their documentation with custom data.We know that
@storybook/web-components
does exist and allows extending the documentation with acustom-elements.json
, though the possibilities of information to add is too limiting for us. Also when using@storybook/web-components
returning a template string from a Story, it isn't turned into HTML but rendered as a serialized string in stories in the "Docs" tab.The text was updated successfully, but these errors were encountered: