-
Notifications
You must be signed in to change notification settings - Fork 245
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
Add Linter (Solium) #59
Conversation
Currently WIP, all issues that don't create a breaking change will be handled
Thanks for taking the time, great work! :) My brain hurts with the doubled indentation. How does everyone feel about it? |
@izqui I prefer the 4 spaces personally |
I can switch it back to 2 spaces and change the Solium settings if that's the preference. I just went with defaults. Personally I think 4 spaces is easier to read but I'm an outsider. |
Let's do 4 :)
… I can switch it back to 2 spaces and change the Solium settings if that's
the preference. I just went with defaults. Personally I think 4 spaces is
easier to read but I'm an outsider.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAbTYEii5ZDMkMf7Lnv6kiVAgw6psygAks5sPHUugaJpZM4OafvP>
.
|
@Quazia sorry, some major refactoring has been going on so there are a few conflicts |
No problem. The non-trivial errors/warnings are still present as well as the parser error related to the solidity-parser repo. If you want to merge in in spite of this I can clean up the conflicts? |
Yeah we'd definitely appreciate it, we can try to fix the bigger issues in a different PR. I'd rather get this in before any other conflicts. |
Alright, conflicts should be handled now. Should I add issues for the non-trivial errors and warnings? |
I think last merge created some more conflicts |
Alright I'll handle them first thing this morning, hopefully I'll be able to get ahead of it this time! |
Alright, I believe everything should be sorted out now. The only rule I disabled was mixed_case as I assume since most instances are functions this would be a breaking error. The only other warning still present is:
There's also still 2 instances of the parser error triggered by solidity-parser:
Hopefully this issue with the parser will be resolved. In one place the statement |
WIP merge, this PR when finished will address issue #53. For more information on the progress see the issue. So far only non-breaking fixes have been applied but not all warnings/errors have been handled so far.