Add functionality to `prefer-import` rule to restrict / auto-fix global types that might have the same name as local types

brandongregoryscott / eslint-plugin-collation

ESLint plugin for making your code easier to read, with autofix and TypeScript support

https://eslint-plugin-collation.brandonscott.me

Apache License 2.0

4 stars 0 forks source link

Add functionality to `prefer-import` rule to restrict / auto-fix global types that might have the same name as local types #74

Closed brandongregoryscott closed 3 months ago

brandongregoryscott commented 3 months ago

For example, if your project has a type named Node or Comment that shadows the Node or Comment interfaces available from the global DOM types, it can be annoying to import these manually, since TypeScript will always "see" them and instead give you typing errors for mismatched properties. Sometimes, it doesn't even seem to suggest an import from the local project.

github-actions[bot] commented 3 months ago

:tada: This issue has been resolved in version 1.4.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: