Rule proposal: No useless template string, or prefer String()

[marcospgp]

Please describe what the rule should do:
Disallow useless template strings, such as ${x}. The thing is this can be used as a way to cast a variable to string, which means the rule could instead be "prefer String()" or "prefer .toString()".

What category of rule is this? (place an "X" next to just one item)

[ ] Warns about a potential error (problem)
[X] Suggests an alternate way of doing something (suggestion)
[ ] Enforces code style (layout)
[ ] Other (please specify:)

Provide 2-3 code examples that this rule will warn about:

const x = "soomething";
callAFunction(123, "mamamia", `${x}`);

const x = 19
callAFunction(123, "mamamia", `${x}`);

Why should this rule be included in ESLint (instead of a plugin)?

Because eslint already had tons of no-useless-something rules, so this one would fit very well with the rest.

Are you willing to submit a pull request to implement this rule?
No unless you point me to the right resources and ask nicely and I have enough free time this week

[mdjermanovic]

Hi @marcospgp , thanks for the rule proposal!

This might as well be a new option in no-implicit-coercion?

[marcospgp]

Hey @mdjermanovic , seems like a good fit.

[eslint-deprecated]

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.

[anikethsaha]

Reopening as there is an active PR for this #13579

[anikethsaha]

+1 to have it as an option for no-implicit-coercion

[eslint-deprecated]

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.

[ljharb]

This should be reopened since there’s an active PR for it.

[yeonjuan]

Reopened. There is an active PR #13579

[eslint-deprecated]

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.

[remcohaszing]

This should be reopened. There's still an active PR that's awaiting feedback from the ESLint team.