Burton Smith

It looks like those are working. You can also add links within your descriptions using markup.

I think you're missing the dash after "Documentation". ` * @reference Button Documentation - https://shoelace.style/components/button`

It looks like I was able to find the issue and I pushed a patch. Let me know if you run into any other issues. @troyvassalotti does the `ctrl` +...

Let me play with it. I think `properties` should for sure be included since they won't appear in the autocomplete.

@Lookwe69 is there a reason you're not creating a base class and extending from that? ```ts class BaseClass extends mixinFunc(HTMLElement) {} class MyElement extends BaseClass { ... } ```

I don't believe the CEM will capture and store the information the same way. By setting it as a variable, it won't be captured as a declaration and be able...

"computed types" like these, generics, and other TS functions are difficult for the analyzer to parse. I haven't found a good way to do that yet. Out of curiosity if...

It looks like this is working in my new package: https://wc-toolkit.com/documentation/type-parser/ Here is an example: https://stackblitz.com/edit/stackblitz-starters-but1bogc?file=src%2Fmy-component.ts

@nikita-rudenko Closing as this has moved to the [WC Toolkit](https://wc-toolkit.com/documentation/type-parser/). Please let me know if you are still experiencing any issues.

@nnaydenow this one is kind of a unique use case and seems very problematic. I believe the changes you proposed would break the privacy inheritance for properties using the TypeScript...