eslint-plugin-lit
eslint-plugin-lit copied to clipboard
lit-html support for ESLint
I'm introducing Lit Element into [my Polymer 3 project](https://github.com/home-assistant/home-assistant-polymer/pull/1738). I won't be able to convert all elements to Lit from the get go and so have a mix of Polymer...
A good linting rule could be to ensure people aren't making a typo in the static properties getter, or use incorrect modifiers: ``` // a function static properties() { return...
It should warn when doing DOM manipulation outside of the render function. Basically not modifying the shadowRoot directly. Resource: https://lit-element.polymer-project.org/guide/templates#design-a-performant-template
Given the following code: ```html ``` I'm getting linting errors on both the lines of `page-url` AND `.count`:   Changing the value of `page-url` to any string (like for...
This is similar to https://github.com/jest-community/eslint-plugin-jest/blob/main/src/rules/unbound-method.ts The jest plugin checks whether the unbound method is valid in the context of jest, or it falls back to the typescript-eslint/unbound-method rule. It would...
These are currently marked as invalid: - `@click=${() => this.#onRetry(file)}` - `@click=${async () => await this.#onDelete(file)}` I believe they are false positives since the arguments to the method do not...
Template literals used as values for the `css` and `svg` tag functions are vulnerable to the same issues with invalid escape sequences as the `html` tag function. For example the...
There is the `no-native-attributes` rule: https://github.com/43081j/eslint-plugin-lit/blob/master/docs/rules/no-native-attributes.md But we also want to avoid native properties like `className`: https://developer.mozilla.org/en-US/docs/Web/API/Element/className We should have a different rule? Or just add more elements to the...
As far as I can see, this plugin does not further lint the `svg` function input from `lit`. But the rules that apply to the `html` syntax should also be...
We should provide an option that lists (string) subclass names, so that ```ts export class IsReallyALitElement extends FooElement { /*...*/ } ``` lints up with our plugin