Greg Oledzki
Greg Oledzki
@dilanarandara do you have sample code showing the problem?
Can you link to an example showing how it would look like?
Instead of attaching a patch file, I suggest you create a Pull Request toward the repository.
Not sure if this is documented anywhere, but currently `setAnnotationsPosition` taking values from the range of `[0.0, 1.0]` is for placing the values **within** the bar. 0 makes it, the...
(Edited your text for formatting, I hope you don't mind)
As to the actual suggestions: - re 1 - I think the standard solution to this is to avoid overloading in such case, i.e. name the methods differently. What is...
Do we even have support to skip some inspections for some Scala versions? I guess we need to add that.
Answering myself, we do have support for enabling/disabling inspections per Scala major version, e.g.: https://github.com/sksamuel/scapegoat/blob/5c690f685632d4b784fb0a187ef0091ec395a233/src/main/scala/com/sksamuel/scapegoat/inspections/collections/PredefSeqIsMutable.scala#L16
I think this is the article by @nrinaudo on the same topic: https://nrinaudo.github.io/scala-best-practices/oop/always_override.html
Understood. Thanks for chipping in! I think we can implement that and if someone is against it, they can disable the rule. I bet we have other controversial rules already.