lint-action: ESlint usage incompatible with `eslint.config.js`
This action’s default usage of --ext when using the eslint linter prevents the action from running when using the modern eslint.config.js flat file configuration.
This problem seems to have been highlighted by three other parties in #730, #739, and #759 but those issues were not addressed.
If there is no critical reason that this can’t be updated, please keep this one open for discussion if possible. I would be happy to PR a fix for this myself if there are no major obstacles or objections.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 37
- Comments: 16 (3 by maintainers)
Commits related to this issue
- fix eslint action: see https://github.com/wearerequired/lint-action/issues/788#issuecomment-2551626087 — committed to panfiva/atomic-crm by panfiva 2 years ago
Any traction on this one ? We use this action and would like to support the v9 flows, Seems theres a PR already to add support
For now one can use the fork from the PR to get things working
So does that mean this action doesn’t support eslint v9? If not, do you guys have any recommendation that does?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If you look at the PR log for this project, the last merge was in July 2024. None of the threads on this topic have comments from maintainers (that I can tell). And @rkuykendall’s PR got auto-closed due to inactivity. Realistically, I wouldn’t expect a new PR to get any more traction until the maintainers chime in with willingness to support this issue.
I’m happy to report that @edlouth’s suggestion worked. Simply replacing
…with…
…was a drop-in fix. Thank you, @rkuykendall!
I think this may be a fix: https://github.com/wearerequired/lint-action/pull/799
I just had it only use ext if the argument is passed in.
I can’t tell how to test it or use it on my own repo though.