-
-
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
Web-components: Custom Elements Manifest v1 support #15138
Web-components: Custom Elements Manifest v1 support #15138
Conversation
Nx Cloud ReportCI ran the following commands for commit 56d28eb. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
@thepassle feels free to ping me on discord if you need help I would be glad to try to help 😉 |
…ariables, also fix stories to display docs with custom elements manifest info
@thepassle I think you were just an export away 😉 I push a couple of commits to add JSDoc on the component used in the WC kitchen sink, add an NPM Script to run the analyzer easily and it looks like it is working: On the screenshot you will see that the descriptions are empty for the properties even if I added some in the JSDoc, I think it's because I activated the
I think we should merge these 2 objects describing the same property. Do you think it's something that could/should be changed on Notes: I set a specific version of TypeScript using Yarn's resolution because we need to update Yarn before being able to us the latest version, this isn't related to this PR. |
Thats odd — that should not be the case. Let me doublecheck this in the analyzer
Doh 🤦♂️🤦♂️🤦♂️ |
@gaetanmaisse The duplicate fields appearing the manifest bug should be fixed in I think we also need to add some docs to document how to use the new version of the manifest, do we need anything else to move forward with this PR? |
@gaetanmaisse @shilman I've updated the documentation 🙂 |
@@ -47,26 +48,30 @@ | |||
"@storybook/source-loader": "portal:../../lib/source-loader", | |||
"@storybook/theming": "portal:../../lib/theming", | |||
"@storybook/ui": "portal:../../lib/ui", | |||
"@storybook/web-components": "portal:../../app/web-components" | |||
"@storybook/web-components": "portal:../../app/web-components", | |||
"typescript": "4.2.4" |
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.
Notes: I set a fixed version to avoid compat' issue with the Yarn 2 version we are using for now
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.
LGTM 🚀
Notes: e2e errors are not related to this PR, see #15411
Merged! Thanks for the PR @thepassle and let see what could be the next improvements on that topic :) |
Awesome! Thanks so much for the help on this 🙂 Do you have any indication on when this will get released? |
6.4-alpha = release later today see #15355 |
Hello! It seems that it does not handle the |
@edoardocavazza new issue please! 🙏 |
@thepassle one final thing I would like to ask of you. If you don't mind popping into our Discord Server and message me (same username) to follow up on a couple of items. |
Issue:
What I did
This adds support for the V1 version of the Custom Elements Manifest schema. This change is non breaking
TODO:
How to test
If your answer is yes to any of these, please make sure to include it in your PR.