-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TODO #14
Comments
duaraghav8
changed the title
deprecate deprecated-suicide rule in solium
TODO (once bounty PRs are merged)
Nov 13, 2017
I've found that there's actually some tests failing. Is it tests error or the linter? |
Tests could fail due to various reasons, the primary one being if you're running solium on windows. |
I'm running on linux mint, please. The errors are actually tests that fail. 1) [RULE] no-abstract-func: Rejections
should reject contracts that use abstract functions:
AssertionError: expected 0 to be 1
+ expected - actual
-0
+1
at Assertion.fail (node_modules/should/cjs/should.js:275:17)
at Assertion.value (node_modules/should/cjs/should.js:356:19)
at Context.<anonymous> (test/no-abstract-func.js:57:34)
2) [RULE] no-void-returns: Rejections
should reject functions that have a void return:
AssertionError: expected 0 to be 1
+ expected - actual
-0
+1
at Assertion.fail (node_modules/should/cjs/should.js:275:17)
at Assertion.value (node_modules/should/cjs/should.js:356:19)
at Context.<anonymous> (test/no-void-returns.js:48:34)
3) Checking package.json
should enforce fixed versions on certain dependencies:
AssertionError: expected false to be true
at Assertion.fail (node_modules/should/cjs/should.js:275:17)
at Assertion.value (node_modules/should/cjs/should.js:356:19)
at fixedDevDeps.forEach.fdd (test/packagejson.js:24:59)
at Array.forEach (<anonymous>)
at Context.done (test/packagejson.js:23:22) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
no-assign-params
message to point out the exact param that's being modified instead of just mentioning function nameno-explicit-visibility
rule.v0.2.0
) + package.json tests (just like in Solium)list-of-rules.tgn
Types of refinement to be done
recommended
= true/falsetype
(default severity or switched off) (Shareable config for the strict security rules? Ethlint#142)The text was updated successfully, but these errors were encountered: