eslint ./some-file.js triggers invalid-todo-violation-rule for unrelated files

[buschtoens]

When linting only a subset of files by explicitly passing them to eslint (instead of just eslint .), all TODOs from all other files are incorrectly reported as passing / invalid-todo-violation-rule.

Steps to reproduce:

1. Setup a package with an eslint config and some files failing that config.
   (Optionally verify, that violations are present with: eslint .)
2. Run UPDATE_TODO=1 eslint --format @scalvert/eslint-formatter-todo .
3. Verify, that violations are no longer reported:
   eslint --format @scalvert/eslint-formatter-todo .
4. Lint a single file eslint --format @scalvert/eslint-formatter-todo ./some-file.js

Actual Behavior

All TODOs for files other than some-file.js are incorrectly reported as fixed (invalid-todo-violation-rule).

Expected Behavior

Only TODOs for files matching the input glob / files list passed to eslint should be checked.

[scalvert]

Thanks for reporting, @buschtoens. I'll take a peek and see what I can find.

I do know of a discrepancy between how the ember-template-lint implementation and this formatter behave, in that the former operates on a file by file basis when working with todos, while the eslint formatter operates on all files. I believe this is likely not what we want, and could be contributing to what you're observing. I plan on cleaning up this implementation and matching it with that of ember-template-lint once I complete a current round of feature enhancements.

[scalvert]

Hey @buschtoens. I just updated and released https://github.com/scalvert/eslint-formatter-todo/releases/tag/v1.4.0, which I believe will address your issue. Please try it out and let me know if it works for you!