Release Notes - SonarSwift - Version 1.4 - HTML format

New Feature

  • [SONARSWIFT-41] - Rule: Conditional compilation should not be used
  • [SONARSWIFT-59] - Rule: Identical expressions should not be used on both sides of a binary operator
  • [SONARSWIFT-88] - Rule: Modulus results should not be checked for direct equality
  • [SONARSWIFT-100] - Rule: Closure expressions should not be nested too deeply
  • [SONARSWIFT-115] - Rule: Floating point numbers should not be tested for equality
  • [SONARSWIFT-128] - Rule: Enumeration types should comply with a naming convention
  • [SONARSWIFT-129] - Rule: Enumeration members should comply with a naming convention
  • [SONARSWIFT-130] - Rule: Implicitly unwrapped optionals should not be used
  • [SONARSWIFT-137] - Rule: Semicolons should not be used
  • [SONARSWIFT-140] - Rule: Backticks should not be used around symbol names
  • [SONARSWIFT-142] - Rule: Trailing closure syntax should not be used when multiple parameters are of function type
  • [SONARSWIFT-145] - Rule: Force-unwrapping of optionals should not be used
  • [SONARSWIFT-147] - Rule: Argument of function type should be the last
  • [SONARSWIFT-157] - Rule: Operator functions should call existing function
  • [SONARSWIFT-158] - Rule: Associativity and precedence of built-in operators should not be changed
  • [SONARSWIFT-159] - Rule: Infix operators that end with "=" should update their left operands

Task

Improvement

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.