Skip to content
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

Addon-docs: Fix prop table default value for web-components #9086

Merged
merged 1 commit into from
Dec 7, 2019

Conversation

steel
Copy link
Contributor

@steel steel commented Dec 6, 2019

Issue:

The work in progress specification for custom-elements.json uses the defaultValue key rather than default. Currently, the default value is not displayed in the props table because this is mapped incorrectly.

https://github.com/webcomponents/custom-elements-json/pull/8/files

What I did

I updated the mapping.

@vercel
Copy link

vercel bot commented Dec 6, 2019

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/storybook/monorepo/daxxw3ixv
🌍 Preview: https://monorepo-git-fork-steel-custom-element-json-defaultvalue.storybook.now.sh

Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any peer dependencies that need to be updated? Or documentation?

Or something else? This change seems too small, unless it's just a bug.

@steel
Copy link
Contributor Author

steel commented Dec 7, 2019

Just a bug.

@shilman shilman added this to the 5.3.0 milestone Dec 7, 2019
@shilman shilman added bug and removed dependencies labels Dec 7, 2019
@shilman shilman changed the title Addon-docs: fix(web-components): update key to reflect specification Addon-docs: Fix prop table default value for web-components Dec 7, 2019
@shilman shilman merged commit 3e9f0fc into storybookjs:next Dec 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants