lit-analyzer
lit-analyzer copied to clipboard
runem
Monorepository for tools that analyze lit-html templates
### Context This was inspired (and maybe closes) https://github.com/runem/lit-analyzer/issues/283. The first commit went in a bad direction (which encouraged self-closing syntax (that doesn't exist in HTML)). Second commit changes the...
Initially I didn't use [`compilerOptions.paths`](https://www.typescriptlang.org/tsconfig#paths), but I'm now adding that to the project. Presence of that setting in `tsconfig.json` does not affect lit-analyser, but as I started gradually replacing imports...
It looks like `lit-analyzer` disallows setting `?disabled` to an async directive. It will throw `no-invalid-directive-binding`: ``` The 'asyncReplace' directive can only be used within a text binding. 56: ?disabled=${asyncReplace(shouldDisable)} no-invalid-directive-binding...
It would be nice if `lit-analyzer` allowed settings event listeners to (well-typed) `asyncReplace` instances. Here's a simple (though somewhat silly) example where the click function changes depending on the date...
I often set a directive as potentially undefined: ```ts ` doSomething()) : undefined} >... ` ``` `lit-analyzer` flags this as incorrect: ``` Type 'DirectiveResult | undefined' is not a Lit...
The [Open VSX release](https://open-vsx.org/extension/runem/lit-plugin) is quite old. It would be awesome if Open VSX could be updated each release just like the Visual Studio Marketplace. Thank you!
Simplest reproduction: ```js html`${() => null}` ``` I expect the arrow `=>` to have the same color.
See [this page](https://lit.dev/docs/components/events/) from the docs. > If you're not using decorators, you can customize event listener options by passing an object to the event listener expression. The object must...
Test to not report missing element type definitions when tag names which are static class properties
Test which proves _no-missing-element-type-definition_ is not reported when the tag name is a static class property. Requires runem/web-component-analyzer#279
Not sure if this is an issue with the plugin, or some other config as part of vscode, but after adding a new tag (`define`), I'm not seeing my editor...
