Question about cyclomatic complexity for pattern match about altcover HOT 2 CLOSED

There is no such exemption currently.

Rather than using a multiway branch, there are, of course, other approaches to the same end that move the branching to system code, such as

let FtdErrorStrings = [(FtdError.InvalidHandle, "Invalid Handle(s) given")
...
                       (FtdError.OtherError, "Undefined Internal USB Error")]
		      |> Map.ofList
...
let FtdiErrorToString (code:FtdError) =
  FtdErrorStrings
  |> Map.tryFindKey code
  |> Option.defaultValue "Undefined Error code returned"

or from a resource file with similar key/value data,

  <data name="FtdError.InvalidHandle" xml:space="preserve">
    <value>Invalid Handle(s) given</value>
  </data>
...
  <data name="FtdError.OtherError" xml:space="preserve">
    <value>Undefined Internal USB Error</value>
  </data>
  <data name="Undefined+FtdError" xml:space="preserve">
    <value>Undefined Error code returne</value>
  </data>

and

let resourceManager = System.Resources.ResourceManager([resource name], Assembly.GetExecutingAssembly())
...
let FtdiErrorToString (code:FtdError) =
  match resourceManger.GetString("FtdError." + code.toString())
  | null -> resourceManger.GetString("Undefined+FtdError")
  | value -> value

which allows you to localize error messages as required.

There are other techniques using attributes on the enum values, but that would require it to be an enum that you define.

from altcover.

Hello Steve,

Thank you for your response and for the suggested solution. I have just implemented the first suggestion in my code and the complexity for this method has dropped from 34 to 5.

from altcover.