lit-analyzer
lit-analyzer copied to clipboard
Monorepository for tools that analyze lit-html templates
This PR excludes ES symbol types from unions when checking bindings. This ensures that `nothing` and `noChange` are ignored in type checking. We remove all symbol types because it is...
Hello, I have the below rule settings in my VS Code's `settings.json` ``` "lit-plugin.rules.no-incompatible-property-type": "off", "lit-plugin.rules.no-incompatible-type-binding": "off", ``` However, the plugin still highlights errors with `no-incompatible-type-binding`.
```ts styled` color: red; ` ``` Currently, it can highlight but cannot autocomplete.
i'm having this pretty frequently by now, for some reason, when i declare a property ```ts @property({type : Object}) public declare myProperty : MyType; ``` and do literally the same...
the following code causes the lit-plugin to show lots of errors, because it doesn't detect it as valid syntax: ```css *:has(> input) { ... } ``` of course i'm using...
According to the `vscode-css-languageservice` documentation, it supports configuration via the [`css.customData`](https://github.com/Microsoft/vscode-css-languageservice/blob/main/docs/customData.md) setting. However, the `vscode-lit-plugin` does not appear to honor these settings when analyzing `css` templates. For example, it should...
I just tried https://github.com/runem/lit-analyzer/tree/master/packages/ts-lit-plugin with https://github.com/WebReflection/uhtml and it works well for their `html` template literals too. I suspect it works with others too. > I am using it with neovim's...
this is a feature i'm waiting for a very long time. assume you dispatch a CustomEvent ``` this.dispatchEvent(new CustomEvent("my-event", { detail: {myProperty: 'whatever'} }); ``` and then you listen to...