-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
fixed linter warnings & moved linting to a separate CI job #677
Conversation
d6cf251
to
b337e1a
Compare
Why can't we remove the else? What is this syntax try ... else? Why can't it be avoided? |
I don't follow… Removing it is exactly what I did 😅
…Yes, this isn't obvious at a glance, so this syntax is somewhat discouraged; it can be replicated explicitly by using boolean flags or |
Wouldn't the following work?
|
OK. I saw the initial |
That is, as of now it's hard to tell (without digging into logs) if the checks fail because of linting, or because the code doesn't work correctly. |
We do need to check the logs on a failure. Please make the code change only. |
At this moment, you couldn't even tell that master is passing all tests because it doesn't pass linting; doing the linting separately would make it much easier to tell what needs to be fixed (and reduce the amount of attempts necessary to fix erroneous pull-requests). |
OK. If that makes things simpler. |
As per discussion in f00348e & #676