Closed codekoriko closed 1 month ago
I was able to reproduce this locally, by taking a new typescript sample project, adding the solhint plugin, running solhint --init
and updating the config to:
{
"extends": "solhint:recommended"
}
On running npx hardhat check
we don't get a non-zero exit code:
Because of this I think https://github.com/protofire/solhint/pull/554
Opened the issue https://github.com/protofire/solhint/issues/572
Thanks @madlabman, we will keep this open to track the issue coming in on the hardhat-solhint
plugin.
@kanej just a heads up this was fixed in Solhint 5.0.1 :rocket:
Just note that upgrading to Solhint 5.0.1 would equate to a major
version bump in the hardhat-solhint
plugin.
Thanks for the report! This issue has now been fixed in the release @nomiclabs/hardhat-solhint@4.0.0
Version of Hardhat
2.22.2
What happened?
I'm using the hardhat-solhint plugin, when the litting process raise error, the exit code stays the 0, therefor command chaining with && don't break, which is a problem
Minimal reproduction steps
Running the linter as mentioned in the doc:
An error arise during the linting but Exit Code stays 0
Search terms
No response