We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Our ESLint configuration is loosely based on XO.
We should first review what configurations are unnecessary and remove them.
Then, there are a bunch of disabled lint rules.
@typescript-eslint/no-unsafe-*
unicorn/no-null
unicorn/prevent-abbreviations
Next, some tseslint tweaks might be helpful
recommended-strict
strict-boolean-expressions
prefer-readonly
ban-ts-comment
Finally, we should consider if these other plugins would be useful:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Our ESLint configuration is loosely based on XO.
We should first review what configurations are unnecessary and remove them.
Then, there are a bunch of disabled lint rules.
@typescript-eslint/no-unsafe-*
(mostly blocked on Support for JSDoc type assertions typescript-eslint/typescript-eslint#1682) (Better TS #302)unicorn/no-null
unicorn/prevent-abbreviations
(needs a lot of configuration to prevent changing src, etc in variable names)Next, some tseslint tweaks might be helpful
recommended-strict
tseslint rulesstrict-boolean-expressions
is niceprefer-readonly
ban-ts-comment
could use some configuring from the default (Standardize comments #217)Finally, we should consider if these other plugins would be useful:
The text was updated successfully, but these errors were encountered: