"semi-spacing" rule doesn't work after "while"

Tell us about your environment

• ESLint Version: 5.16.0
• Node Version: 10.15.3
• npm Version: 6.4.1

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

{
  "env": {
    "es6": true,
    "node": true,
    "jasmine": true
  },
  "extends": "eslint:recommended",
  "parserOptions": {
  },
  "rules": {
    "semi-spacing": "error"
    "prefer-arrow-callback": "error",
    "no-else-return": "error",
    "no-multi-spaces": "error",
    "no-whitespace-before-property": "error",
    "camelcase": "error",
    "new-cap": "error",
    "no-console": "error",
    "comma-dangle": "error",
    "no-var": "error",
    "no-shadow": "error",
    "object-shorthand": [
      "error",
      "properties"
    ],
    "indent": [
      "error",
      4,
      {
        "SwitchCase": 1
      }
    ],
    "quotes": [
      "error",
      "single"
    ],
    "semi": [
      "error",
      "always"
    ]
  }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

while (/*condition*/) ;

./node_modules/.bin/eslint ./lib

What did you expect to happen?

To error about the space between the end of while condition and ;, because of the "semi-spacing": "error" rule. This issue is specific to one-line (or empty) while statements.

What actually happened? Please include the actual, raw output from ESLint.

It passes.

Are you willing to submit a pull request to fix this bug?

Maybe.

[platinumazure]

@mysticatea You removed the “tsc agenda” label about a month ago but I don’t see any information here on what the TSC chose to do with this. Could you please add that information and then, if necessary, reopen this issue? Thanks!

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.