Skip to main content

ADR 0004: Angular Change Detection Strategy

Date: 2025-09-07

Status: Deprecated

Context​

Previously, Angular was established as the framework of choice for frontend applications, necessitating a decision on its change detection strategy. However, with the adoption of a framework-agnostic approach for frontend development (as detailed in ADR 0003), the specific change detection strategy within Angular is no longer a universally relevant architectural concern for new projects. This ADR is therefore deprecated as its core subject matter is no longer applicable to our current frontend strategy.

Decision​

This Architectural Decision Record is deprecated. The decision regarding Angular's change detection strategy is no longer binding for new frontend development within the Citadel project, as Angular is no longer the mandated or primary frontend framework. Teams choosing to use Angular for specific applications should make their own informed decisions regarding change detection, considering the context of their specific project.

Consequences​

Positive​

  • Increased Flexibility: Teams are no longer constrained by a project-wide decision on Angular's change detection, allowing them to choose the most appropriate strategy for their specific Angular-based projects (if any).
  • Reduced Overhead: The need to maintain and enforce this specific Angular-related architectural decision across the entire project is eliminated.

Negative​

  • Potential for Inconsistency (within Angular projects): If multiple teams independently choose Angular, there might be variations in their change detection strategies. However, this is an acceptable trade-off given the overall framework-agnostic direction.