-
**Describe the issue**
When adopting the Angular rules we had resolved to not adopt Angular's Recommended Extras configuration of @typescript-eslint/no-inferrable-types. [See resolution comment](ht…
-
### Before You File a Documentation Request Please Confirm You Have Done The Following...
- [X] I have looked for existing [open or closed documentation requests](https://github.com/typescript-esli…
-
There are aspects of this plugin that don't support eslint v9
`TypeError: context.getAncestors is not a function`
from this line
https://github.com/ember-cli/eslint-plugin-ember/blob/7e6bca993226…
-
I see the readme says:
Usage with TypeScript
To enable working with TypeScript projects, install @babel/preset-typescript as a dependency, then add "typescript" to parserOptions.babelOptions.parse…
-
Once the rules start to pile up, it's easier to keep them in separate files. Currently I have this in `index.js`:
```js
const fs = require("node:fs");
const path = require("node:path");
const …
-
The two ESLint JSDoc rules used by this template and your other add-ons were deprecated in 2018: https://eslint.org/blog/2018/11/jsdoc-end-of-life/ and it looks like they might be removed soon: https:…
-
These symbols are currently generated but with `@deprecated` annotations. We should either adjust `eslint` rules to error when using deprecated methods or even better ensure the bindgen tool doesn't p…
-
### Which @angular/* package(s) are relevant/related to the feature request?
core
### Description
Apologizes for using the wrong issue template here: this is a **tooling** suggestion for this repos…
-
There are a couple of types that are imported without the `type` signifier and thus unused:
https://github.com/threlte/threlte/blob/6ebc7cffdef5bf0e10201e26d15850cace13cd2f/packages/extras/src/lib/…
-
## Proposed change
Add eslint package containing a base rule set for the UI library, Utils lib, and the actual app, have them set to use the `warn-only` plugin to not interrupt current function but r…