APP-2482: remove unnecessary ESLint and TypeScript rules #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Disable some rules that have been giving us grief:
ESLint
no-undef-init
andunicorn/no-useless-undefined
@typescript-eslint/no-unsafe-assignment
andsonarjs/no-duplicate-string
.svelte
, turn offsonarjs/no-unused-collection
because it crashes ESLintno-confusing-void-expression
so we're not forced to use a bunch of braces in event handlersTypeScript
noPropertyAccessFromIndexSignature
, because it's a purely stylistic concern, and it interacts poorly with with Svelte when components are accessed fromRecord
objects