This repository has been archived by the owner on Sep 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cdosborn
force-pushed
the
lint-medium-strictness
branch
2 times, most recently
from
September 10, 2018 23:05
a5f7ff3
to
4944f63
Compare
cdosborn
force-pushed
the
lint-medium-strictness
branch
2 times, most recently
from
September 10, 2018 23:25
cbfa908
to
e1aa39e
Compare
cdosborn
changed the title
Make linter quite a bit more strict
Make linter significantly more strict
Sep 10, 2018
cdosborn
force-pushed
the
lint-medium-strictness
branch
2 times, most recently
from
September 11, 2018 19:54
8ca45da
to
5d084a2
Compare
Any tips for reviewing 250+ commits? 😱 |
lol, at the top you'll see there are 464. I don't expect you to review each one. Look at the handful of commits that touch more than one file (or more than one line), maybe try and understand those. Or look at the commit messages and find any linting errors you don't understand and look at those. |
calvinmclean
approved these changes
Sep 12, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying all of my questions! Looks good and I am excited to have cleaned up code to work with
…nt' is assigned to but never used
… is assigned to but never used
…to but never used
… to but never used
…d to but never used
…signed to but never used
…imported but unused
… to but never used
cdosborn
force-pushed
the
lint-medium-strictness
branch
from
September 12, 2018 23:10
5d084a2
to
12fed6e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Increase linter from "low" to "medium"
Each commit fixes a single lint violation. I don't expect a reviewer to look at each commit. There are only a handful of commits that change more than one line, and they all fell into the same category of issue relating to imports.
File A, would
from foo import X
, but A would never use X at all. So the linter would suggest to remove that import. However file B, would importX from A
. So file B would have to be updated to also import fromfoo
. A file should import a value from the package where the value is defined.Checklist before merging Pull Requests