[x] Did you run the analyzer with the --dev flag to get more information?
[x] Did you create a minimal reproduction in the playground?
Completing the items above will greatly improve triaging time of your issue.
Expected behavior
This was already discussed on slack previously, so adding here as a reminder, and for visibility. Here is a minimal reproduction
In brief, given a mixin like this:
export function SlotMixin(superClass) {
/**
* @slot foo - i was hoping CEM would pick up on this, so i could document the slot just once, on the mixin.
*/
class SlotElement extends superClass {
renderSomeSlot() {
return html`<slot name="foo"></slot>`;
}
}
return SlotElement;
}
Checklist
--dev
flag to get more information?Completing the items above will greatly improve triaging time of your issue.
Expected behavior
This was already discussed on slack previously, so adding here as a reminder, and for visibility. Here is a minimal reproduction
In brief, given a mixin like this:
And a component like this:
I would hope that CEM would pick up the jsdoc comments and apply it to
MyElement
, but this is not the case.Here are some pointers that were linked to on slack:
output.json
is what the analyzer outputsfixture/custom-elements.json
is what you expect the output to be (this file is 'handwritten'/edited)package/
is the folder that will get analyzed during the test run