From d8616e66cb556c3665cc2d7cb9881dfa91449f34 Mon Sep 17 00:00:00 2001 From: Marcel Menk Date: Sat, 25 Oct 2025 08:56:38 +0200 Subject: [PATCH] feat: ngrx facade pattern --- .../src/lib/page/rules/rules.component.html | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/libs/domains/landingpage/frontend/feature-framework/src/lib/page/rules/rules.component.html b/libs/domains/landingpage/frontend/feature-framework/src/lib/page/rules/rules.component.html index cab9123..0e2d2fa 100644 --- a/libs/domains/landingpage/frontend/feature-framework/src/lib/page/rules/rules.component.html +++ b/libs/domains/landingpage/frontend/feature-framework/src/lib/page/rules/rules.component.html @@ -426,6 +426,11 @@
Frontend Applications (scope:frontend)
Frontend applications SHOULD integrate design system libraries consistently. +
  • + Frontend applications SHOULD use SCSS for styling. CSS + MAY be used only when SCSS is not available or not supported by the build + tooling. +
    • State Management Guidelines
    @@ -495,6 +500,17 @@
    State Management Guidelines
    Frontend applications MUST respect dependency boundaries when implementing state management across domains. +
  • + Frontend applications MUST use facades to abstract state management from + components. Components MUST NOT directly access the store or dispatch + actions. Facades SHOULD be provided in data-access libraries + and expose a type-safe, domain-specific API for components to interact with state. +
    • +
  • + For simple state management patterns (Signals, BehaviorSubjects), components + MAY interact with state directly through services, but + SHOULD still use facades for complex state scenarios. +
    • Backend Applications (scope:backend)