Bug: [no-useless-template-literals] Comments are removed by auto-fix

[JoshuaKGoldberg]

Before You File a Bug Report Please Confirm You Have Done The Following...

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I have searched for related issues and found none that matched my issue.
• I have read the FAQ and my problem is not listed.

Playground Link

https://typescript-eslint.io/play/#ts=5.3.3&fileType=.ts&code=AYQwJA3g9AVABAIzjKcDkBjNdZwCbJQC%2BApsANxA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6Jge1tmUSWWS18iALbF4AQ2G1Gw6BPioMkRNGgdokcGAC%2BIHUA&tsconfig=&tokens=false

Repro Code

`a${/* b */ 'c' /* d */}e`;

ESLint Config

module.exports = {
  "rules": {
    "@typescript-eslint/no-useless-template-literals": "error"
  }
}

tsconfig

{
  "compilerOptions": {
    // ...
  }
}

Expected Result

The fix result should be... well, I'm not sure what. Maybe the comments should be moved to before the string?:

// b
// d
`ace`;

Actual Result

`ace`;

Additional Info

This is a common thing to look out for in rule reviews. Ref: #8549

[bradzacher]

personally I'm okay with removing the comments there.
I don't think there's much value in keeping them. I also would say that in a provably useless template literal the odds of having comments is very low.

[JoshuaKGoldberg]

`Hello, ${/* TODO: Switch to the user's name once the API works (GH-1234) */ 'user'}!`;

I think cases like this would be rare, but not impossible.

[bradzacher]

I think cases like this would be rare, but not impossible.

Hence 😄

the odds of having comments is very low

I'd personally be okay with closing this with a comment saying "please file a new issue if you run into this and we'll fix it". I doubt anyone would ever run into it in reality though