`no-unused-vars` and `prefer-template` rules conflict
See original GitHub issueHaving the following code:
var someString = giveMeMyString();
this.paragraph = `some article with $(someString)`;
I get no-unused-vars
error.
If I change it to:
var someString = giveMeMyString();
this.paragraph = 'some article with ' + someString;
I get prefer-template
error.
How it’s possible no one came across this? Am I doing something wrong?
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
ESLint - Configuring "no-unused-vars" for TypeScript
Is there any way to configure the no-unused-vars rule to take these two cases into account? I'm not a fan of disabling the...
Read more >eslint-config-adidas-es5 | Yarn - Package Manager
ESLint base configuration and rules for all JavaScript codebases ... Updated no-unused-vars config to match @typescript-eslint/no-unused-vars .
Read more >vue/no-v-for-template-key-on-child
This rule reports the key of the <template v-for> placed on the child elements. ... Don't enable both rules together; they are conflicting....
Read more >ESLint | Webdesign Advanced - Netlify
Prettier and ESLint have a few common rules that (may) conflict with each other; In the index page, ESLint doesn't work inside the...
Read more >no-unused-vars - ESLint - Pluggable JavaScript Linter
Rule Details. This rule is aimed at eliminating unused variables, functions, and function parameters. A variable foo is considered to be used if...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah thank you! I blame context switching between Ruby, Bash and JS 😃
@chris-mac can you provide the code in question? Note that the “correct syntax” refers to the backticks, NOT single/double quotes, surrounding the literal.