Disable import/named in the TypeScript configuration #1726
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.
As I was linting our projects, I noticed a few violations across them:
Looking around, it seems the recommendations are to either use
import type
(I haven't tried) or disabling the rule locally.I was wondering what this rule brings when used in a TypeScript setup and realized I am not the only one.
Since it makes sense to disable the rule when using TypeScript, and this rule is enabled by the
recommended
preset, would it be a ridiculous idea to disable it in thetypescript
preset of this repo, and save consumers the inconvenience of doing it locally?(I'm sure some of these could also be disabled, but I figured I would ask your opinions on this one first before looking at others)