Greg Oledzki
Greg Oledzki
At my org we have received the following notification from Slack:  Let's understand it and deal with it somehow. I bet we are affected. >>> As a contributor or...
Amending tests introduced in #189 to actually not only parse the JSON, but also the check how does the resulting Scala case class looks like. That is done by comparing...
When trying to release `0.2.12` `sbt ++publishedSigned` raised the following errors: ``` [...] [error] source : /home/mccartney/git/slack-scala-client/target/scala-2.11/slack-scala-client_2.11-0.2.12-javadoc.jar.asc [error] destination: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/github/slack-scala-client/slack-scala-client_2.11/0.2.12/slack-scala-client_2.11-0.2.12-javadoc.jar.asc [error] If you have a staging repository that has failed,...
https://github.com/sksamuel/scapegoat static analysis tool reports several warnings in our code base: > Scapegoat Inspections > Errors 7 Warnings 8 Infos 4 > > slack.SlackUtil.scala:10 > Error Use of unsafe Traversable...
Another attempt at #565, i.e. fixing #564. The previous attempt got reverted because of some `NullPointerExceptions`
Currently the code is full of `System.out.println` statements. Some/most of them being commented out, some of them not. The industry standard practice is to employ a logging framework (log4j, commons-logging,...
Current [inspection levels](https://github.com/scapegoat-scala/scapegoat/blob/master/src/main/scala/com/sksamuel/scapegoat/Level.scala) are: `ERROR`, `WARNING`, `INFO`. I suggest to add a new one: (working name) `SKIP`. So that for instance one can set it as a default level for...
## The idea I suggest we introduce a configuration file (at least optionally). ## Context With override levels and disabling inspections we already have possibly quite a few values to...
I continue to be impressed about the concept and execution of @scala-steward. It automates the boring stuff and serves remediations in an undoubtedly convenient way for the project maintainers. How...