Allow comments after // eslint-disable-line <rule-name>

The version of ESLint you are using. 5.12.1

The problem you want to solve. I’ve just filed an issue against an incorrect (in my opinion) application of a rule. I want to disable that rule in my code, and mention why I’ve done so:

// eslint-disable-line no-unsafe-finally because https://github.com/eslint/eslint/issues/11297

Including the URL on the same comment line is handy because I can click it from my IDE and check on the status, then remove the entire comment once the issue is fixed.

Another use case is simply explaining why a rule was removed.

Your take on the correct solution to problem.

eslint should ignore non-rule comments following // eslint-disable-line <rule-name>.

eslint.org demo.

[kaicataldo]

There is currently an RFC open for this: https://github.com/eslint/rfcs/pull/33

Please track the issue there.

[JvJefke]

@kaicataldo

Why is this solution better than having two comments? i.e.

You’re example is not really a real life one. This one is (kinda):

const someFunction() =>
    // Map the otherData to this list by index
    // https://github.com/eslint/eslint/issues/11298
    response.data.map((item, idx) => (item._templateMeta = otherData[idx])) // eslint-disable-line [some-rule]

There is more visual correlation between te “real” comment than the eslint comment which makes it just confusing. If you could do something like OP suggests, it isn’t:

const someFunction() =>
    // Map the otherData to this list by index
    response.data.map((item, idx) => (item._templateMeta = otherData[idx])) // eslint-disable-line [some-rule] because https://github.com/eslint/eslint/issues/11298

So I do think this solution is better than the workaround you suggested.