Description

I migrated some code from React to template strings, but missed adding the $ sign around the curly braces so I had

Hello {name} instead of Hello ${name}

I did not see any existing eslint rules that warn against this. I also wasn't sure what the best rule set to propose this rule to, but I like eslint-plugin-unicorn a lot and wasn't sure this quite had the 'universality' that it would be a core eslint rule.

Somewhat similar rule in eslint core rule set https://eslint.org/docs/latest/rules/no-template-curly-in-string#examples

They say when proposing a new rule to eslint core to justify e.g. "Why should this rule be in the core instead of a plugin?

In general, we prefer that rules be implemented in plugins where they can be tailored to your specific use case.". not sure this rule has enough justification?

Fail

var replace = `Hello {name}`;

Pass

const replace = `Hello ${name}`;

Additional Info

No response