Release Notes - SonarSwift - Version 1.3 - HTML format

New Feature

  • [SONARSWIFT-116] - Rule: Sequential tests should not check the same condition
  • [SONARSWIFT-117] - Rule: The ternary operator should not return the same value regardless of the condition
  • [SONARSWIFT-118] - Rule: Files should not be empty
  • [SONARSWIFT-119] - Rule: Classes should not have too many lines
  • [SONARSWIFT-120] - Rule: Functions and variables should not be defined outside of classes
  • [SONARSWIFT-121] - Rule: Types should be defined in separate source files
  • [SONARSWIFT-122] - Rule: Protocol names should comply with a naming convention
  • [SONARSWIFT-123] - Rule: Field names should comply with a naming convention
  • [SONARSWIFT-125] - Rule: Functions should not contain too many return statements
  • [SONARSWIFT-126] - Rule: "switch case" clauses should not have too many lines
  • [SONARSWIFT-127] - Rule: Functions and closures should not be empty
  • [SONARSWIFT-131] - Rule: "get" should be omitted in read-only computed properties and subscripts
  • [SONARSWIFT-132] - Rule: Top-level definitions should have access control modifier
  • [SONARSWIFT-133] - Rule: Operator definitions should be surrounded by whitespaces
  • [SONARSWIFT-141] - Rule: "break" should be the only statement in switch "case"
  • [SONARSWIFT-143] - Rule: "return" should be omitted from single-expression closures
  • [SONARSWIFT-144] - Rule: Useless parentheses around expressions should be removed to prevent any misunderstanding

Improvement

  • [SONARSWIFT-108] - Rule S1075 - update rule functionality to match edited specification
  • [SONARSWIFT-114] - Rule: Jump statements should not be used unconditionally
  • [SONARSWIFT-134] - S115: Change parameter default value
  • [SONARSWIFT-146] - Name convention rules: do not consider back ticks as part of identifier

Edit/Copy Release Notes

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