fix: use @typescript-eslint/no-unused-vars #221
Merged
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.
Aegir currently relies on typescript to perform two linter rules, which is annoying for reasons mentioned in the above issue.
noFallthroughCasesInSwitch
noUnusedLocals
This PR makes typescript rules more strict to enforce both of these conditions.
For
noFallthroughCasesInSwitch
, it appears that thestandard
eslint rule set already includes theno-fallthrough
rule.So this PR only needs to enforce
noUnusedLocal
, and we just add@typescript-eslint/no-unused-vars
.