HighFile-scopeC# Plug & play

Mark Unchanged Variables as `const`

Ensure that variables that never change are marked as const to prevent accidental modification and enhance code clarity.

Add to Mesrai Open workspace

Why this matters

Variables that never change should be marked as const to prevent accidental modification and improve code clarity.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

public bool Seek(int[] input)
{
  var target = 32;  // Noncompliant
  foreach (int i in input)
  {
    if (i == target)
    {
      return true;
    }
  }
  return false;
}

Prefer

public bool Seek(int[] input)
{
  const int target = 32;
  foreach (int i in input)
  {
    if (i == target)
    {
      return true;
    }
  }
  return false;
}

Related rules

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening

Why this matters

Bad vs. good

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes

Why this matters

Bad vs. good

Related rules

Avoid Duplicating String Literals

Avoid Empty Methods

Avoid modifying built-in prototypes