Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upScala Checkstyle warnings #196
Comments
ruebot
added
the
question
label
Apr 11, 2018
This comment has been minimized.
This comment has been minimized.
Short answer is "yes" in my opinion in the long run (maybe before 1.0.0 release). We should try to pick these off, as best we can. Only caveat is this compared to other priorities. |
ruebot
added this to To Do
in 1.0.0 Release of AUT
Apr 13, 2018
This comment has been minimized.
This comment has been minimized.
Use Some of the requested changes could change behavior, so this will need to be tested pretty heartily before being accepted. |
This comment has been minimized.
This comment has been minimized.
Partially addressed with 77dbd51 |
ruebot
closed this
in
004ce1f
Aug 9, 2018
1.0.0 Release of AUT
automation
moved this from To Do
to Done
Aug 9, 2018
ruebot
added a commit
that referenced
this issue
Aug 8, 2019
This comment has been minimized.
This comment has been minimized.
LOL, 364 days since the last commit on this issue. |
This comment has been minimized.
This comment has been minimized.
Every August 8th, our project commits to addressing Scala Checkstyle warnings. |
ianmilligan1
added a commit
that referenced
this issue
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ruebot commentedApr 11, 2018
Now that we've resolved #176 and #184, and implemented the equivalent of Checkstyle for Scala, do we want to resolve these Scala Checkstyle warnings?