-
Notifications
You must be signed in to change notification settings - Fork 33
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
Scala Checkstyle warnings #196
Comments
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. |
Use Some of the requested changes could change behavior, so this will need to be tested pretty heartily before being accepted. |
Partially addressed with 77dbd51 |
- Remove all underscore imports, except shapeless - Address all scalastyle warnings - Update scalastyle config for magic numbers, and null (only used in tests)
LOL, 364 days since the last commit on this issue. |
Every August 8th, our project commits to addressing Scala Checkstyle warnings. |
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?
The text was updated successfully, but these errors were encountered: