Thanks for the PR, @bradzacher!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

👋 @bradzacher, just checking in - still interested in this PR?

I think this still makes sense to have.
Some people have the preference to name imports the same as their module name - which naming-convention can't enforce, but there are other rules for that.

I think that for those that don't care about matching - it would be useful to be able to enforce naming of the imports.
It's been super low pri for me though as there's not huge amount of call from the community for this.

Closing for housekeeping purposes.
Anyone is free to raise a fresh PR to continue this work!