Rune Mehlsen

Hi Nick, thanks for creating this issue and making me aware of it! First of all, lit-plugin right now runs with a very old version of web-component-analyzer. Testing what you...

Update: Support for nullable JSDoc type is now live in version [1.1.6](https://marketplace.visualstudio.com/items?itemName=runem.lit-plugin) of the vscode plugin. You can add `"lit-plugin.rules.no-incompatible-type-binding": "off"` to your vscode settings to disable type checking while...

Hi, thanks for reporting this. I think I will need an example of how the `@param` JSDoc tag can be used to document the properties of detail. Right now you...

I agree that it would be valuable, but I will only implement it in the experimental JSON format when we agree on something at https://github.com/webcomponents/custom-elements-json. Please read those discussions and...

There exists two PR's with concrete suggestions on how the format could look :-) The problem right now with the experimental JSON format that `web-component-analyzer` outputs, is that it becomes...

Here is an update of what TODO's are still needed on my side: There are still some things that have not been implemented yet, specifically: **TODO:** (updated to reflect newest...

I implemented most of what's in the updated schema. While implementing the changes, I wrote down a couple of questions that I would like to discuss. 1. What is the...

Thanks for your issue! This plugin uses properties and types from `lib.dom.d.ts`. Here are some of the properties on `HTMLInputElement`: ```typescript interface HTMLInputElement extends HTMLElement { ... value: string max:...

@bennypowers Thanks for reporting this issue :-) Here are my thoughts: * We don't have access to LitElement-related metadata if consuming custom elements from a library, so we have to...

Do you think all arrays should be sorted alphabetically (attributes, properties, events, slots and cssProperties) or only CSS custom properties? In that case I'll make sure to sort them all.