Apply the @typescript-eslint/eslint-recommended rules to .gts files
#475
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default these rules are only applied to a whitelist of extensions, and .gts isn't part of that. To work around that issue we apply the rules ourselves for now.
Windvis
commented
Mar 11, 2024
| @@ -16,11 +21,12 @@ module.exports = { | |||
| // ts files | |||
| { | |||
| files: ['**/*.{gts,ts}'], | |||
| extends: [ | |||
| 'plugin:@typescript-eslint/eslint-recommended', | |||
There was a problem hiding this comment.
This is already part of the @typescript-eslint/recommended config, and we don't really need it in either case, since we include the rules ourselves now.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default these rules are only applied to a whitelist of extensions, and .gts isn't part of that. To work around that issue we apply the rules ourselves for now.
This fixes an issue we noticed in #474