-
Notifications
You must be signed in to change notification settings - Fork 26
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
Example for vanilla js web components #48
Comments
Yes would love to see how this integrates with Lit components as well |
I'm using a combination of
It picks up my components just fine without even any JSDoc. Although the functions my components expose aren't there Sample output```json { "name": "quote-box", "source": { "module": "./src\\wcomps\\quote-box.ts", "symbol": "QuoteBox" }, "attributes": [ { "name": "endpoint", "required": false, "priority": "normal", "value": { "type": "string", "required": true } } ], "js": { "properties": [ { "name": "endpoint", "required": false, "priority": "normal", "value": { "type": "string", "required": true } }, { "name": "_loading", "required": false, "priority": "lowest", "value": { "type": "boolean", "required": true } }, { "name": "_quote", "required": false, "priority": "lowest", "value": { "type": "Quote", "required": true } } ] } }, ```Edit: I don't want to rely on the author of this package to fix the forementioned issues, so I took the matters into my own hands with Atulin/web-component-analyzer. I also fixed reference paths on Windows while I was at it. |
@Atulin thanks for the information. Let's wait for the PR to be merged and than I'll update documentation: runem/web-component-analyzer#239 (review) |
WebStorm and other IDEs support Custom Elements Manifest since 2023.2, so you don't really need to generate Web types for components themselves, unless you need some support for patterns. The |
Can you please add an example for vanilla web components?
The text was updated successfully, but these errors were encountered: