@abdonrd Unfortunately I've had some problems with my hands (it's slowly getting better), so I had to pause OSS development in the meantime. The Lit team has been really kind to offer their help on preparing lit-analyzer for the next version of Lit, so you can expect some updates soon 🙂
@btopro I haven't yet finished the work on upgrading web-component-analyzer to v1.0.0 for this plugin, but you can follow the work in this issue :-) https://t.co/PVQVkbi7Mh
📣 Announcing <api-viewer> element 0.1.0
📖 UI for web-component-analyzer by @RuneMehlsen
🖋 Document your custom elements API
⚙️ Properties, attributes, events, slots
🛠️ Supports markdown in JSDoc comments
https://t.co/E61resIHGa
@kennethrohde@justinfagnani@rictic @momondo My excitement already started at Polymer Summit 2017 where lit-html was announced 🎉 But your talks definitely also takes part in it! Please do more of them 🙌
@kennethrohde@daKmoR@code web-component-analyser is generic and focused on analyzing attrs,props,events,eg on Web Components built with any library but isn’t focus on how it’s rendered. The lit CLI would include all that and then also analyze the html as well. Im open for just having one single CLI tho :)
A new version of lit-plugin for @code is out now 🎉
⚡️ Autocompletion for attributes, properties, events and slots
💅 CSS support out of the box
🔥 Improved web component analyzer
📝 Supports vscode custom html data format
https://t.co/mfSHUNwlmk
@adamdbradley@kennethrohde@daKmoR@code Right now the library analyzes the typings outputted by stencil. This makes it possible to provide an excellent IDE experience for using web components made with stencil :-)
@daKmoR@code I actually built a general web component analyzer that provides linting and documentation generation for web components and I’m planning on extracting lit-plugin functionality into a lit specific CLI: https://t.co/TK4TKrWIly
@daKmoR@code Thanks! :-) I have been following that thread closely which resulted in the custom html data format as of now. I will work on supporting formats that we agree on in the community.
@justinfagnani@kennethrohde@code I agree! I added the list because people were confused of the difference. The lit-html vscode plugin is a great plugin and I’m also describing its strengths in the section before the comparison list :-)
I just published "lit-plugin": a vscode plugin that adds type checking, code completion and highlighting for lit-html. It automatically finds web components in your code and libraries! Please give it a try and tell me what you think :-) https://t.co/mfSHUNwlmk
@lastmjs@kennethrohde I have also opened an issue regarding making it possible for lit-plugin to find tag names based on custom functions as expanding HTMLElementTagNameMap can be a bit cumbersome.
https://t.co/ZGgI8qJd0y
@lastmjs@kennethrohde Regarding lit-plugin not finding props on custom elements please see the issue I just created on the repository: https://t.co/OorjdSVMjb
As for using your own custom element function I recommend that you expand the HTMLElementTagNameMap TS interface (see example in the readme)
@lastmjs@kennethrohde How did you define the property? Right now it only looks at properties with the lit-element property-decorator and not general public fields on the class. Ill take a look at improving it this weekend :-)