Overview / Introduction
Since the Angular team is moving towards zoneless framework strategy, we need to prepare Journey application for that and to improve application and for better maintainability we need to use recommended signal api to replace zone based change detection to push change detection.
Acceptances Criteria
AC 1: Identity places where signal can be used instead of decorators such as input, output and viewChild, viewContent
AC 2: Replace implementation with signal api
AC 3: Prefer standalone and signal based components to increase reusability
AC 4: Use Push change detection policy
AC 5: Fix sonar issues as much as if possible
AC 6: Remove unused/empty scss files
Overview / Introduction Since the Angular team is moving towards zoneless framework strategy, we need to prepare Journey application for that and to improve application and for better maintainability we need to use recommended signal api to replace zone based change detection to push change detection.
Acceptances Criteria AC 1: Identity places where signal can be used instead of decorators such as input, output and viewChild, viewContent AC 2: Replace implementation with signal api AC 3: Prefer standalone and signal based components to increase reusability AC 4: Use Push change detection policy AC 5: Fix sonar issues as much as if possible AC 6: Remove unused/empty scss files
Additional Contexts