Skip to main content

Typed rule semantic analysis flow

This chart focuses on the semantic path used by the plugin's current typed branches, especially immutable-data and readonly-array.

Maintainer interpretation​

  • Treat semantic calls as a guarded path, not a default path.
  • getTypeOfNode(...) is the main reliability bridge between ideal type information and resilient fallback behavior.
  • Missing services currently lead to conservative degradation rather than a hard failure.

Operational checkpoints​

  1. If users report missing typed precision, verify parser service availability first.
  2. If semantic branches become expensive, add syntax-level short-circuits before type operations.
  3. Keep fix/suggestion decisions conservative and local to the rule.