Skip to content
Snippets Groups Projects
Commit 03e4a4a5 authored by Benjamin Kott's avatar Benjamin Kott Committed by Oliver Hader
Browse files

[TASK] Cleanup eslint configuration

We renamed the eslint configuration to follow the recommended standards
so developers IDEs will pick up the configuration more easily.

The ruleset was adapted to follow a wider range of recommendations.
- eslint:recommended
- @typescript-eslint/recommended
- lit/recommended
- wc/recommended

In addition we now also force more kinds of spacing rules to avoid
IDEs having different opinions on how to format for example includes.

The only recommendation we don't want to follow is
- @typescript-eslint/no-inferrable-types.
We don't want to disallow being explicit.

Instead of turning off rules we cannot fully fulfill as of now, we are
now changing the configuration to warning. This will help developers
spotting mistakes more easy when writing code.

Rules that are currently in "warn" mode:
- @typescript-eslint/ban-types
- @typescript-eslint/no-explicit-any
- @typescript-eslint/no-this-alias

To only check for errors run in the Build directory:
- npx eslint ./Sources/TypeScr...
parent 0b3e0b56
Branches
Tags
No related merge requests found
Showing
with 264 additions and 182 deletions
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment