how to fix codacy alert “Generic Object Injection Sink”
来源： https://stackoverflow.com/questions/51715616/how-to-fix-codacy-alert-generic-object-injection-sink
codacy
how to fix codacy alert “Generic Object Injection Sink”
来源： https://stackoverflow.com/questions/51715616/how-to-fix-codacy-alert-generic-object-injection-sink
Scala avoid using null
问题 I hava a project on github that is analysed by codacy . The analysis suggest to "Avoid using null" for the following line of code: def doSomethingWithPath(path:Path) = { require(path != null, "Path should not be null") //<-to avoid ... } What is the simplest scala idiomatic thing to do to fix it? 回答1: I would keep it as is. You aren't really using null here, just guarding against it. The alternative could be to just delete that line altogether, and decide to not handle the null at all.
What advantages does scala.util.Try have over try..catch?
Searching online for the answer gives two prominent posts ( Codacy's and Daniel Westheide's ), and both give the same answer as Scala's official documentation for Try : An important property of Try shown in the above example is its ability to pipeline, or chain, operations, catching exceptions along the way. The example referenced above is: import scala.io.StdIn import scala.util.{Try, Success, Failure} def divide: Try[Int] = { val dividend = Try(StdIn.readLine("Enter an Int that you'd like to divide:\n").toInt) val divisor = Try(StdIn.readLine("Enter an Int that you'd like to divide by:\n")
What advantages does scala.util.Try have over try..catch?
问题 Searching online for the answer gives two prominent posts (Codacy's and Daniel Westheide's), and both give the same answer as Scala's official documentation for Try: An important property of Try shown in the above example is its ability to pipeline, or chain, operations, catching exceptions along the way. The example referenced above is: import scala.io.StdIn import scala.util.{Try, Success, Failure} def divide: Try[Int] = { val dividend = Try(StdIn.readLine("Enter an Int that you'd like to
Why is it bad pratice calling an array index with a variable?
问题 I'm currently developing a little game in Javascript and i'm using Codacy to review my code and help me cleaning it. One of the most seen error is Generic Object Injection Sink (security/detect-object-injection). It happens when i'm trying to access a value in an array using a variable. Like in this example : function getValString(value) { var values = ["Misérable", "Acceptable", "Excellente", "Divine"]; return values[value]; } This function is used to display on screen the value's