Closed amb26 closed 2 years ago
It looks like the root failure is caused by running a version of node that is too old to actually execute current eslint correctly (the 10.x version mentioned) - but the overall run should still be flagged as a failure
Yes, there's a single line to change, I'll test for side effects and ask you to confirm that it behaves as expected for you.
Describe the bug
A clear and concise description of what the bug is.
To reproduce
Steps to reproduce the behavior: Check out https://github.com/cindyli/preferencesServer/tree/proxy-sso-impl currently at commit 98871b705a67523f2869d511d6c75380ee72b6ad run npm install run npm lint
Expected behavior
There is a failing ESLint check in this repository. The lint run should be marked as a failure -
The output from the run is as follows:
It seems that all eslint checks have failed, and 23 files are marked in error - but the overall run is marked as a success.
ubuntu version 20.0.4, node version 10.19.0, npm version 6.14.4 fluid-lint-all version 1.1.5