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

Official-storybook: Prop table example for multiple named exports #9364

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

shilman
Copy link
Member

@shilman shilman commented Jan 9, 2020

Issue: N/A

What I did

Simple proof of concept example for named exports

subcomponents

How to test

See official-storybook

@shilman shilman requested a review from usulpro as a code owner January 9, 2020 04:41
@vercel
Copy link

vercel bot commented Jan 9, 2020

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/51csjv7sk
✅ Preview: https://monorepo-git-shilman-prop-tables-from-named-exports.storybook.now.sh

@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 2020

Fails
🚫

PR is not labeled with one of: ["cleanup","doc-dependencies:update","BREAKING CHANGE","feature request","bug","documentation","maintenance","dependencies:update","dependencies","other"]

Generated by 🚫 dangerJS against 2d22ca8

@shilman shilman changed the title Official-storybook: Add prop table example for multiple named exports Official-storybook: Prop table example for multiple named exports Jan 9, 2020
@shilman shilman added addon: docs maintenance User-facing maintenance tasks labels Jan 9, 2020
@shilman shilman added this to the 5.3.0 milestone Jan 9, 2020
@shilman
Copy link
Member Author

shilman commented Jan 9, 2020

Self-merging @ndelangen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addon: docs maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant