-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
feat: add web-component #175
feat: add web-component #175
Conversation
Looks good to me - I'll be more than happy to check the README again as a user when switching from our custom build. |
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
just 2 things:
- it should be published to
@asyncapi/web-component
- can we rename
async-api-web-component.js
toasyncapi-web-component.js
and any otherasync-api
occurances too? - you need to have this https://github.com/asyncapi/html-template/blob/master/package.json#L28-L30 in package.json of webcomponent otherwise first publishing to npm will fail
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@derberg I propagated your suggestions to PR :) |
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
let's see if it works 😄
🎉 This PR is included in version 0.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Changes proposed in this pull request:
Improve web component to be production ready:
web-component
folder,Related issue(s)
See also #148
@gexclaude if you would like to, I invite you to check the PR, especially the changes in readme :)