-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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: Props / Description for web-components #8585
Conversation
This pull request is being automatically deployed with ZEIT Now (learn more). 🔍 Inspect: https://zeit.co/storybook/monorepo/hk204nohr |
4a2ec47
to
f32d7c3
Compare
f32d7c3
to
97a19ab
Compare
97a19ab
to
7e3fce6
Compare
75c4316
to
c6349f2
Compare
c6349f2
to
05bf22e
Compare
05bf22e
to
6bfd548
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SUPERB!!! 🏆
@daKmoR Thank you for this contribution! I have a question regarding the way how this json is generated. Is it possible to automate this process of generation of properties? |
@alazurenko it's documented in the addon-docs... maybe we should move that info to |
@daKmoR Thank you for help! |
Hello @daKmoR quick question for you - should properties be called 'props' for web components? 🤓 |
hmm properties would probably be better 🤔 care to create a PR and update it? 🤗 |
Sure thing. PR is created here. |
Issue:
What I did
custom-elements.json
How to test
open kitchen sink docs mode
Still open
=> if approach looks good I will add documentation for it 👍
as now.sh is currently having some trouble here is a screenshot how it will look like