Thanks for the issue!This is an extension rule. That means we take the base rule and extend it to support TS syntax or features.We don't break from the base rule to add new features unless they are specifically related to TS.In this instance - this request is not related to TS, thus we shall not implement it. If you'd like to see it, feel free to raise a request with the ESLint team.

The fix has been merged to master, and will be released Monday, as per our [release schedule](https://github.com/typescript-eslint/typescript-eslint#versioning)If you need it sooner, please try the `canary` tag on NPM.

With any issue in opened in this project - it either has a visible progress in the form of an attached PR, or it has no progress.We are a community run project. The **volunteer** maintainers spend most of their time triaging issues and reviewing PRs. This means that most issues *will not progress* unless a member of the community steps up and **champions** it.If this issue is important to you - consider being that champion.If not - please just subscribe to the issue and wait patiently.Commenting asking for status updates does not bump issue priority in any way and just serves to spam ***everyone*** subscribed to the issue.

We are a community run project. The **volunteer** maintainers spend most of their time triaging issues and reviewing PRs. This means that most issues *will not progress* unless a member of the community steps up and **champions** it.If this issue is important to you - consider being that champion.If not - please use the subscribe function and wait patiently for someone else to implement.

As per [our contributing guidelines](https://github.com/typescript-eslint/typescript-eslint/blob/master/CONTRIBUTING.md#addressing-feedback-and-beyond) this PR is in the queue of PRs to reviewed, and will be reviewed when we are able.This project is run by volunteer maintainers, so it might be a bit before we can find the time to get to it.

We ***STRONGLY*** recommend you use automatic code formatters like [prettier](https://www.npmjs.com/package/prettier).Stylistic lint rules take a lot of effort to write, require ongoing maintenance to add more configuration as people want to fit their preferences, and are a large burden to maintain as new syntax is added.The configurability also leads to huge fanout [making tests huge, and awful to maintain](https://github.com/typescript-eslint/typescript-eslint/blob/b814e635c1f34139c89e0176727480935dd45cac/packages/eslint-plugin/tests/rules/type-annotation-spacing.test.ts).It's for these reasons that [eslint has frozen all stylistic lint rule options, and will not accept any new ones](https://eslint.org/blog/2020/05/changes-to-rules-policies).