Naming and Contract Alignment

Why this rule exists

Renaming Delete to Get keeps the old behavior but advertises a new contract. Callers see Get and assume safety; the method still deletes. Rename refactors must match new behavior, not just new vocabulary.

Code example

- public void DeleteOrder(int id) { _repo.Remove(id); _repo.Save(); }
+ public void GetOrder(int id)  { _repo.Remove(id); _repo.Save(); }

- public void DeleteOrder(int id) { _repo.Remove(id); _repo.Save(); }
+ public Order GetOrder(int id) => _repo.Find(id);
+ public void DeleteOrder(int id) { _repo.Remove(id); _repo.Save(); }

Configuration

Disable or adjust the severity of this rule in .gauntletci.json:

{
  "rules": {
    "GCI0047": { "enabled": true, "severity": "Info" }
  }
}

See Configuration for the full schema.

Related rules

Discussed in