no-unused-vars firing incorrectly on args inside template-tag about eslint-plugin-ember HOT 7 CLOSED

Oh, right.
Does it make a difference of its a gts or gjs file?

from eslint-plugin-ember.

This fails ❌

<template>
  {{#each array as |item index|}}
    {{index}}
  {{/each}}
</template>

This passes ✅

someFunction((item, index) => console.log(index));

Conceptually, they are the same, so the eslint result should be the same for both examples.

Eslint docs say

unused positional arguments that occur before the last used argument will not be checked, but all named arguments and all positional arguments after the last used argument will be checked.

from eslint-plugin-ember.

Ah! Thanks for that clarification! I didn't know they differentiate with prior positionals!

from eslint-plugin-ember.

Does _item also get reported as unused?

from eslint-plugin-ember.

Underscores don't seem to make any difference out-the-box. Calling it _item, or _ doesn't make any difference

If I configure an eslint argsIgnorePattern, then underscored variables can be ignored:

/*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/

const array = [];

<template>
  {{#each array as |_item index|}}
    {{index}}
  {{/each}}
</template>

^^ this passes ✅

But this argsIgnorePattern is not default eslint behaviour, so I imagine most projects rely on the default 'args: after-used'' behaviour.

from eslint-plugin-ember.

Same issue in both gjs and gts 😓

from eslint-plugin-ember.

Isn't this correct behavior tho?
(Am i missing something? 😅)

from eslint-plugin-ember.