Compare commits

...

215 Commits

Author SHA1 Message Date
Nino
a9a80a192e feature(libs-remission): Improvements and Refactoring of Remission List Component
Ref: #5340
2025-12-16 17:26:28 +01:00
Nino
3d82e7f0af feature(libs-feature-data-access): Using catchResponseArgsErrorPipe across all data-acesss services now and removed old patterns. Adjusted some tests and added Logging for every case wrapped in try catch patterns
Ref: #5340
2025-12-15 17:48:43 +01:00
Nino
3101e8e8e0 feature(oms-data-access): Removed abortSignals for POST and PUT requests
Ref: #5340
2025-12-11 17:57:55 +01:00
Nino
a3415e450d feature(checkout-data-access, remission-data-access): Removed AbortSignals for POST and PUT requests
Ref: #5340
2025-12-11 17:46:46 +01:00
Nino Righi
de3edaa0f9 Merged PR 2077: fix(checkout-data-access, checkout-reward-shopping-cart, checkout-reward-sele...
fix(checkout-data-access, checkout-reward-shopping-cart, checkout-reward-selection-dialog): Show Low Stock message inside Dialog, Adjusted Item Identifyer so that mergedItems inside reward-selection-dialog service works properly, Adjusted Error Message Logic and Quantity Select Logic based on purchasing Options for Abholung

Ref: #5523
2025-12-10 17:12:47 +00:00
Nino Righi
964a6026a0 Merged PR 2076: fix(common-data-access, crm-data-access): Improved Error handling, handling i...
fix(common-data-access, crm-data-access): Improved Error handling, handling invalidProperties errors corretly inside crm customer card area

Refs: #5528, #5529
2025-12-10 17:11:22 +00:00
Nino Righi
83ad5f526e Merged PR 2075: fix(ui-layout, ui-input-controls, shared-filter): Set overlayPositions inside...
fix(ui-layout, ui-input-controls, shared-filter): Set overlayPositions inside filter-menu-button and outsourced the logic

Ref: #5526, #5477
2025-12-10 09:50:15 +00:00
Nino Righi
ccc5285602 Merged PR 2074: fix(remission): Implementation of Abort Remission Logic
fix(remission): Implementation of Abort Remission Logic

Ref: #5489
2025-12-10 09:48:49 +00:00
Nino Righi
7200eaefbf Merged PR 2073: fix(checkout-reward-shopping-cart): Preselect Purchasing Option Branch if Edi...
fix(checkout-reward-shopping-cart): Preselect Purchasing Option Branch if Edit item

Ref: #5516
2025-12-08 16:51:49 +00:00
Nino Righi
39e56a275e Merged PR 2072: fix(reward-order-confirmation): Only display one orderDate if other ones are...
fix(reward-order-confirmation): Only display one orderDate if other ones are equal

Ref: #5517
2025-12-08 15:20:19 +00:00
Nino Righi
6c41214d69 Merged PR 2071: fix(crm-customer-bon-redemption): Added Date Pipe to Bon
fix(crm-customer-bon-redemption): Added Date Pipe to Bon

Ref: #5521
2025-12-05 20:04:28 +00:00
Nino Righi
6e55b7b0da Merged PR 2070: fix(shared-filter, reward-catalog): Added Branch Filter Toggle to Reward HSC...
fix(shared-filter, reward-catalog): Added Branch Filter Toggle to Reward HSC View, Adjusted Controls Panel Filter Styling and Layout to fix mobile issues and added spacing to order-by-toolbar

Refs: #5514, #5475
2025-12-05 20:04:07 +00:00
Nino Righi
5711a75188 Merged PR 2068: fix(shared-filter): Adjusted Styling parameters for Height and Scrolling
fix(shared-filter): Adjusted Styling parameters for Height and Scrolling

Ref: #5476, #5477
2025-12-05 10:10:32 +00:00
Nino Righi
3696fb5b2d Merged PR 2069: feature(oms-data-access, oms-return-task-list): Return can now handle Rewards
feature(oms-data-access, oms-return-task-list): Return can now handle Rewards

#5373
2025-12-05 10:10:18 +00:00
Nino
7e7721b222 Merge branch 'release/4.5' into develop 2025-12-03 16:00:41 +01:00
Nino
14be1365bd fix(crm-loyalty-cards): Show always Points of first Card 2025-12-03 15:59:08 +01:00
Nino Righi
d5324675ef Merged PR 2067: fix(ui-layout): Ipad Dropdown Scrolling Fix
fix(ui-layout): Ipad Dropdown Scrolling Fix
2025-12-03 14:16:21 +00:00
Nino
f10338a48b Merge branch 'release/4.5' into develop 2025-12-02 17:33:50 +01:00
Nino
aa57d27924 fix(oms-return-details): Label Unknown Fix
Ref: #5513
2025-12-02 17:20:56 +01:00
Nino
6cb9aea7d1 Merge branch 'release/4.5' into develop 2025-12-02 17:18:11 +01:00
Lorenz Hilpert
fdfb54a3a0 Merged PR 2065: ♻️ refactor(core-navigation): remove library and use TabService directly
♻️ refactor(core-navigation): remove library and use TabService directly

Remove @isa/core/navigation library entirely as it was just a thin
wrapper around TabService.patchTabMetadata(). Consumers now use
TabService directly for scoped metadata operations.

Changes:
- Delete libs/core/navigation/ (~12 files, ~2900 LOC removed)
- Update 6 consumer components to use TabService directly
- Remove @isa/core/navigation path alias from tsconfig.base.json
- All operations now synchronous (removed async/await)

Migration pattern:
- preserveContext() → patchTabMetadata(tabId, { [scope]: data })
- restoreContext() → activatedTab()?.metadata?.[scope]
- restoreAndClearContext() → get + patchTabMetadata(tabId, { [scope]: null })

Refs #5502
2025-12-02 15:41:18 +00:00
Nino
5f94549539 fix(oms-return-details): Dropdown Label and Select Bullet Styling Adjustments
Ref: #5513
2025-12-02 16:32:57 +01:00
Nino Righi
aee63711e4 Merged PR 2066: fix(ui-layout, input-controls-dropdown, oms-return-details): prevent stale sc...
fix(ui-layout, input-controls-dropdown, oms-return-details): prevent stale scroll events from closing dropdown on open

Delay scroll listener registration using requestAnimationFrame when
activating CloseOnScrollDirective. This prevents stale scroll events
still in the event queue from immediately triggering closeOnScroll
when opening the dropdown after scrolling.

Also adds conditional rendering for product format and publication date
in return-details-order-group-item component.

Refs: #5513
2025-12-02 14:02:32 +00:00
Nino Righi
a3c865e39c Merged PR 2064: feature(oms-return-details): Display Loyalty Points if order is Reward Order
feature(oms-return-details): Display Loyalty Points if order is Reward Order

Ref: #5374
2025-12-02 12:40:44 +00:00
Lorenz Hilpert
68f50b911d Merged PR 1991: feat(navigation): implement title management and enhance tab system
 feat(navigation): implement title management and enhance tab system

This commit introduces a comprehensive title management system and extends
the tab functionality with subtitle support, improving navigation clarity
and user experience across the application.

Key changes:

Title Management System:
- Add @isa/common/title-management library with dual approach:
  - IsaTitleStrategy for route-based static titles
  - usePageTitle() for component-based dynamic titles
- Implement TitleRegistryService for nested component hierarchies
- Automatic ISA prefix addition and TabService integration
- Comprehensive test coverage (1,158 lines of tests)

Tab System Enhancement:
- Add subtitle field to tab schema for additional context
- Update TabService API (addTab, patchTab) to support subtitles
- Extend Zod schemas with subtitle validation
- Update documentation with usage examples

Routing Modernization:
- Consolidate route guards using ActivateProcessIdWithConfigKeyGuard
- Replace 4+ specific guards with generic config-key-based approach
- Add title attributes to 100+ routes across all modules
- Remove deprecated ProcessIdGuard in favor of ActivateProcessIdGuard

Code Cleanup:
- Remove deprecated preview component and related routes
- Clean up unused imports and exports
- Update TypeScript path aliases

Dependencies:
- Update package.json and package-lock.json
- Add @isa/common/title-management to tsconfig path mappings

Refs: #5351, #5418, #5419, #5420
2025-12-02 12:38:28 +00:00
Nino Righi
0670dbfdb1 Merged PR 2063: fix(domain-checkout): After refreshing cart availabilities always keep previo...
fix(domain-checkout): After refreshing cart availabilities always keep previous selected price from purchasing options modal

Ref: #5488
2025-12-02 11:59:35 +00:00
Lorenz Hilpert
db4f30af86 🔧 chore: improve skills cross-references and CLAUDE.md guidance
- Add --amend option with safety rules to commit command
- Add logging skill cross-references to angular-template and html-template
- Fix logging skill name from logging-helper to logging
- Add extended thinking triggers, context monitoring, and code investigation
  rules to CLAUDE.md
2025-12-02 12:57:27 +01:00
Lorenz Hilpert
39b945ae88 📝 docs: add reference documentation for specialist skills
Add migration-patterns.md for test-migration-specialist (Jest to Vitest)
and zod-patterns.md for type-safety-engineer (Zod validation patterns).
2025-12-02 12:57:11 +01:00
Lorenz Hilpert
a2b29c0525 ♻️ refactor: convert architecture-documentation from command to skill
Move architecture documentation generation from a slash command to a
skill with comprehensive reference materials (C4 model, Arc42, ADR templates).
2025-12-02 12:56:56 +01:00
Lorenz Hilpert
2c385210db 🔧 chore: add frontmatter metadata to docs commands
Add allowed-tools, argument-hint, and description frontmatter to
docs-library.md and docs-refresh-reference.md for better discoverability.
2025-12-02 12:56:40 +01:00
Lorenz Hilpert
46999cc04c 🔧 chore: consolidate quality commands into single quality.md
Merge quality-bundle-analyze.md and quality-coverage.md into a unified
quality.md command with subcommand support (bundle, coverage).
2025-12-02 12:56:20 +01:00
Nino Righi
ee9f030a99 Merged PR 2062: fix(isa-app-customer): Clear Navigation State Context if Customer Area gets d...
fix(isa-app-customer): Clear Navigation State Context if Customer Area gets destroyed

Ref: #5512
2025-12-01 11:25:11 +00:00
Lorenz Hilpert
5aded6ff8e 🩹 fix(ui-input-controls): remove top padding from dropdown options when filter present 2025-11-28 18:18:57 +01:00
Nino Righi
3228abef44 Merged PR 2061: feature(crm-data-access): Added check in customer resource if customerId has...
feature(crm-data-access): Added check in customer resource if customerId has changed to prevent flickering in the view after Filter changes etc.

Ref: #5478
2025-11-28 12:40:04 +00:00
Nino Righi
c0cc0e1bbc Merged PR 2060: feature(checkout-reward, core-tabs): Added back button and configured it so i...
feature(checkout-reward, core-tabs): Added back button and configured it so it can accept optional route to navigate. Added orderNumber and orderDate to reward order confirmation

Ref: #5456
2025-11-28 12:38:08 +00:00
Nino Righi
41630d5d7c Merged PR 2055: feature(ui-label, ahf, warenausgabe, customer-orders): Added and Updated Labe...
feature(ui-label, ahf, warenausgabe, customer-orders): Added and Updated Label Library and Label to the Views, Updated Positioning

Ref: #5479
2025-11-28 12:37:11 +00:00
Nino Righi
7884e1af32 Merged PR 2059: feature(ui-modal): add QR code display for URLs in dialog modals
feature(ui-modal): add QR code display for URLs in dialog modals

Add automatic URL detection and QR code rendering in dialog modals:
- Parse dialog content to extract URLs (http/https)
- Display extracted URLs as QR codes using angularx-qrcode library
- Split content around URL to show text before and after the QR code
- Auto-detect URLs by default, with optional showUrlAsQrCode override
- Add comprehensive unit tests for URL parsing helpers

Ref: #5511
2025-11-27 16:41:51 +00:00
Lorenz Hilpert
a5bb8b2895 Merged PR 2058: feat(crm): customer card copy-to-clipboard and carousel improvements
Customer Card Copy-to-Clipboard (#5508)

  - Click on card number copies it to clipboard using Angular CDK Clipboard
  - Shows success tooltip confirmation positioned on the right
  - Tooltip auto-dismisses after 3 seconds

  Card Stack Carousel Improvements (#5509)

  - Fix card centering by using afterNextRender instead of AfterViewInit
  - Add ResizeObserver to handle dynamic size changes
  - Disable transforms until natural position is measured (prevents initial jump)
  - Center single card in carousel view

  Tooltip Enhancements

  - Add success variant with green styling (isa-accent-green)
  - Add position input (left | right | top | bottom)
  - Add fade in/out CSS keyframes animations (150ms)
  - Respect prefers-reduced-motion for accessibility

  Related Tasks

  - Closes #5508
  - Refs #5509
2025-11-27 16:28:06 +00:00
Lorenz Hilpert
7950994d66 Merged PR 2057: feat(checkout): add branch selection to reward catalog
feat(checkout): add branch selection to reward catalog

- Add new select-branch-dropdown library with BranchDropdownComponent
  and SelectedBranchDropdownComponent for branch selection
- Extend DropdownButtonComponent with filter and option subcomponents
- Integrate branch selection into reward catalog page
- Add BranchesResource for fetching available branches
- Update CheckoutMetadataService with branch selection persistence
- Add comprehensive tests for dropdown components

Related work items: #5464
2025-11-27 10:38:52 +00:00
Nino Righi
4589146e31 Merged PR 2056: fix(ui-tooltip): Integrated CloseOnScrollDirective to close tooltip on scrolling
fix(ui-tooltip): Integrated CloseOnScrollDirective to close tooltip on scrolling

Ref: #5510
2025-11-26 20:08:11 +00:00
Nino
98fb863fc7 Merge branch 'release/4.5' into develop 2025-11-26 16:46:47 +01:00
Nino Righi
6f13d48604 Merged PR 2054: fix(checkout-reward-shopping-cart): Layout Issue Fix
fix(checkout-reward-shopping-cart): Layout Issue Fix

Ref: #5458
2025-11-26 14:04:06 +00:00
Nino Righi
d4bba4075b Merged PR 2053: feature(checkout-reward-cart): Added Empty State and View Adjustments, Disabl...
feature(checkout-reward-cart): Added Empty State and View Adjustments, Disable CTA if no items are in cart

Ref: #5435
2025-11-26 14:03:24 +00:00
Lorenz Hilpert
1fae7df73e 📝 docs: add library-reference.md usage guidance to CLAUDE.md 2025-11-25 14:14:19 +01:00
Lorenz Hilpert
bc1f6a42e6 📝 docs: update README documentation for 13 libraries 2025-11-25 14:13:44 +01:00
Nino Righi
0aeef0592b Merged PR 2052: fix(ui-input-controls): Fix Dropdown Scrolling Issue on IPAD
fix(ui-input-controls): Fix Dropdown Scrolling Issue on IPAD

Ref: #5505
2025-11-25 13:00:58 +00:00
Lorenz Hilpert
aee64d78e2 Merged PR 2051: Fix Card Position
Related work items: #5506
2025-11-25 10:36:25 +00:00
Nino
2c39ca05a9 fix(ui-input-controls): Fix iOS Dropdown Scrolling
Ref: #5505
2025-11-25 10:26:34 +01:00
Nino
5054dd5492 fix(crm-customer-card): Bg White fix 2025-11-24 17:55:12 +01:00
Nino Righi
b93e39068c Merged PR 2050: feature(checkout-reward): Disable Print Order Confirmation for HSC Users
feature(checkout-reward): Disable Print Order Confirmation for HSC Users

Ref: #5471
2025-11-24 16:01:56 +00:00
Lorenz Hilpert
dc26c4de04 Merged PR 2049: feat(oms): add auto-refresh for open reward tasks
feat(oms): add auto-refresh for open reward tasks

Implements 5-minute polling to automatically update open reward tasks
without requiring manual page refresh. Uses reference counting to safely
handle multiple consumers starting/stopping the refresh.

Changes:
- Add startAutoRefresh/stopAutoRefresh methods with ref counting
- Add lifecycle hooks to carousel component for proper cleanup
- Add logging for debugging auto-refresh behavior
- Add refresh interval constant (5 minutes)

Closes #5463

Related work items: #5463
2025-11-24 15:46:17 +00:00
Nino
688390efdb Merge branch 'develop' into release/4.5 2025-11-24 16:21:52 +01:00
Nino Righi
8b852cbd7a Merged PR 2048: fix(shared-barcode, crm-customer-card): improve barcode rendering with transp...
fix(shared-barcode, crm-customer-card): improve barcode rendering with transparent SVG background

Enhance barcode component flexibility by separating container and SVG
background colors. The SVG barcode now defaults to transparent background
while maintaining container background control, enabling better integration
with various card designs.

Changes:
- Add separate svgBackground input for SVG element (default: transparent)
- Keep background input for container styling (default: #ffffff)
- Add containerWidth and containerHeight inputs for flexible sizing
- Update customer card to remove explicit white background on barcode
- Add opacity styling for inactive customer cards
- Enhance test coverage for new background and sizing inputs

The separation of concerns allows the barcode to adapt to parent container
backgrounds while maintaining consistent rendering across different contexts.

Ref: #5498
2025-11-24 14:58:05 +00:00
Lorenz Hilpert
949101a1ed feat: add css-keyframes-animations skill for native CSS animations
Add new skill for creating performant CSS animations:
- Native @keyframes animations with GPU acceleration
- Angular animate.enter/leave for modern view transitions
- Performance guidelines and best practices
- Reference guide for common animation patterns
2025-11-24 14:54:14 +01:00
Lorenz Hilpert
fd0b950f01 📝 docs: add css-keyframes-animations skill to mandatory usage tables
Added css-keyframes-animations skill to documentation:
- Mandatory skill invocation rules table (trigger: creating CSS animations)
- Skill chaining table (component with animations workflow)
2025-11-24 14:53:47 +01:00
Lorenz Hilpert
38de927c4e Merged PR 2047: feat(carousel): convert to transformX with touch support and card animations
feat(carousel): convert to transformX with touch support and card animations

- Convert carousel from scroll-based to translate3d() transform positioning
- Add touch/swipe support with direct DOM manipulation for smooth 60fps performance
- Add mouse drag support for desktop navigation
- Implement hardware-accelerated transforms with will-change optimization
- Add disabled input to prevent navigation when needed
- Fix bounds calculation to use parent viewport width
- Add card stacking animation with translateY and rotation effects
- Remove shadow for cards beyond 3rd position in stacked mode
- Update tests with 4 new disabled state test cases (17 tests total)

Refs #5499

Related work items: #5499
2025-11-24 13:37:34 +00:00
Michael Auer
7429f28bf9 Merge branch 'develop' into release/4.5 2025-11-24 11:47:02 +01:00
Michael Auer
7f1cdf880f ! azure-pipelines.yml: set new and old style docker tag (2 tags) 2025-11-24 11:16:19 +01:00
Michael Auer
acb541df4e Merge branch 'develop' into release/4.5 2025-11-24 09:37:16 +01:00
Michael Auer
9383e2035b Merged PR 2039: New Docker Tag 2025-11-24 08:33:42 +00:00
Lorenz Hilpert
a1a8b1f115 ci: update minor version to 5 in CI configuration 2025-11-21 19:01:19 +01:00
Lorenz Hilpert
ac2df3ea54 ♻️ refactor(agents,skills): optimize invocation system with context-efficient architecture
## Major Changes

**Agent System Overhaul:**
-  Added 3 specialized implementation agents (angular-developer, test-writer, refactor-engineer)
- 🗑️ Removed 7 redundant agents (debugger, error-detective, deployment-engineer, prompt-engineer, search-specialist, technical-writer, ui-ux-designer)
- 📝 Updated all 9 agent descriptions with action-focused, PROACTIVELY-triggered patterns
- 🔧 Net reduction: 16 → 9 agents (44% reduction)

**Description Pattern Standardization:**
- **Agents**: "[Action] + what. Use PROACTIVELY when [specific triggers]. [Features]."
- **Skills**: "This skill should be used when [triggers]. [Capabilities]."
- Removed ambiguous "use proactively" without conditions
- Added measurable triggers (file counts, keywords, thresholds)

**CLAUDE.md Enhancements:**
- 📚 Added "Agent Design Principles" based on Anthropic research
-  Added "Proactive Agent Invocation" rules for automatic delegation
- 🎯 Added response format control (concise vs detailed)
- 🔄 Added environmental feedback patterns
- 🛡️ Added poka-yoke error-proofing guidelines
- 📊 Added token efficiency benchmarks (98.7% reduction via code execution)
- 🗂️ Added context chunking strategy for retrieval
- 🏗️ Documented Orchestrator-Workers pattern

**Context Management:**
- 🔄 Converted context-manager from MCP memory to file-based (.claude/context/)
- Added implementation-state tracking for session resumption
- Team-shared context in git (not personal MCP storage)

**Skills Updated (5):**
- api-change-analyzer: Condensed, added trigger keywords
- architecture-enforcer: Standardized "This skill should be used when"
- circular-dependency-resolver: Added build failure triggers
- git-workflow: Added missing trigger keywords
- library-scaffolder: Condensed implementation details

## Expected Impact

**Context Efficiency:**
- 15,000-20,000 tokens saved per task (aggressive pruning)
- 25,000-35,000 tokens saved per complex task (agent isolation)
- 2-3x more work capacity per session

**Automatic Invocation:**
- Main agent now auto-invokes specialized agents based on keywords
- Clear boundaries prevent wrong agent selection
- Response format gives user control over detail level

**Based on Anthropic Research:**
- Building Effective Agents
- Writing Tools for Agents
- Code Execution with MCP
- Contextual Retrieval
2025-11-21 19:00:01 +01:00
Nino Righi
4107641e75 Merged PR 2046: feature(crm-data-access): Update Transactions Endpoint
feature(crm-data-access): Update Transactions Endpoint

Ref: #5336
2025-11-21 17:39:57 +00:00
Nino
bb717975a0 fix(customer-card-main-view): Take activeCardCode first if it exist
Refs: #5503
2025-11-21 17:13:56 +01:00
Nino
6c75536cd0 Merge branch 'develop' of https://dev.azure.com/hugendubel/ISA/_git/ISA-Frontend into develop 2025-11-21 17:10:51 +01:00
Nino
4c306a213d fix(crm-customer-card): Refresh after Lock, Unlock or Add Cards correctly, Adjusted Placeholder Text, Show Transactions based on first Card instead of first active card
Ref: #5503
2025-11-21 17:10:12 +01:00
Nino Righi
7a98db35fb Merged PR 2045: feature(crm-data-access): Updated Add Card Endpoint
feature(crm-data-access): Updated Add Card Endpoint

Ref: #5329
2025-11-21 15:41:24 +00:00
Nino Righi
cf359954ca Merged PR 2044: fix(utils-positive-integer-input): Fixed issue with copy and paste
fix(utils-positive-integer-input): Fixed issue with copy and paste

Ref: #5501
2025-11-21 15:40:55 +00:00
Nino Righi
df1fe540d0 Merged PR 2043: #5335 Endpoint Unlock wurde erweitert
#5335 Endpoint Unlock wurde erweitert
2025-11-21 14:30:01 +00:00
Lorenz Hilpert
bf87df6273 Merged PR 2042: fix(navigation): prevent autoTriggerContinueFn from persisting across navigat...
fix(navigation): prevent autoTriggerContinueFn from persisting across navigations

The autoTriggerContinueFn flag was remaining in navigation context after
being read, causing incorrect auto-triggering on subsequent page visits.

Changes:
- Add patchContext() method to NavigationContextService and NavigationStateService
  for partial context updates without full replacement
- Update details-main-view.component to use patchContext() to clear the flag
  immediately after reading, while preserving returnUrl
- Add comprehensive JSDoc and README documentation for patchContext()
- Include structured logging for patch operations

The new patchContext() method provides a cleaner API for updating specific
context properties without manually preserving all other properties.

Closes #5500

Related work items: #5500
2025-11-21 13:45:40 +00:00
Lorenz Hilpert
7a6a2dc49d Merged PR 2038: feat(shared,crm): add Code 128 barcode generation library
feat(shared,crm): add Code 128 barcode generation library

Implements new @isa/shared/barcode library with directive and component
for generating Code 128 barcodes using JsBarcode.

Features:
- Standalone Angular directive (svg[sharedBarcode])
- Standalone Angular component (<shared-barcode>)
- Signal-based reactive inputs
- SVG-based vector rendering
- Customizable colors, size, margins, fonts
- Comprehensive Vitest test coverage (39 tests)
- Storybook stories for both directive and component
- Integrated into customer loyalty card component

Changes:
- Created @isa/shared/barcode library with directive and component
- Added JsBarcode dependency (v3.12.1)
- Integrated barcode into customer loyalty card display
- Added Storybook stories for interactive documentation
- Fixed ui-switch story component reference
- Updated library reference documentation

Refs #5496

Related work items: #5496
2025-11-21 13:42:32 +00:00
Lorenz Hilpert
5f1d3a2c7b Merged PR 2040: fix(crm): prevent duplicate reload of loyalty points
fix(crm): prevent duplicate reload of loyalty points

Refactored reload mechanism to use parent-managed pattern:
- Child components emit events instead of reloading directly
- Parent coordinates reload of both transactions and bonus cards
- Added loading guards to prevent concurrent requests
- Added JSDoc documentation to public methods

Closes #5497

Related work items: #5497
2025-11-21 13:40:06 +00:00
Nino Righi
644c33ddc3 Merged PR 2041: fix(ui-input-controls-dropdown): Added Dropdown Backdrop + Lock Position
fix(ui-input-controls-dropdown): Added Dropdown Backdrop + Lock Position

Ref: #5495
2025-11-21 13:35:49 +00:00
Lorenz Hilpert
5f2cb21c18 docs(skill): update library-scaffolder to include architectural tags
- Add Step 4 for automatic library tagging
- Include --prefix parameter in Nx generation commands
- Document tag rules and verification steps
- Update creation report to show tags
- Add references to enforce-module-boundaries config
2025-11-20 17:59:22 +01:00
Nino Righi
b32cc48fd9 Merged PR 2036: feature(libs-icons, crm-customer-card-transactions): Added Refresh Icon, Adde...
feature(libs-icons, crm-customer-card-transactions): Added Refresh Icon, Added Spacer to Transaction Layout, Added Refresh CTA Styling

Ref: #5493
2025-11-20 16:58:02 +00:00
Nino Righi
bcd4d655a6 Merged PR 2035: fix(utils-positive-integer-input, crm-customer-booking, crm-customer-card): a...
fix(utils-positive-integer-input, crm-customer-booking, crm-customer-card): add missing path mapping in tsconfig

Add the @isa/utils/positive-integer-input path mapping to tsconfig.base.json
to resolve module resolution issues. The library was created but the path
alias was not properly registered, causing import errors in consuming modules.

Ref: #5492
2025-11-20 16:57:04 +00:00
Lorenz Hilpert
1784e08ce6 chore: update project configurations to skip CI for specific libraries
Added "skip:ci" tag to multiple project configurations to prevent CI runs
for certain libraries. This change affects the following libraries:
crm-feature-customer-card-transactions, crm-feature-customer-loyalty-cards,
oms-data-access, oms-feature-return-details, oms-feature-return-process,
oms-feature-return-summary, remission-data-access, remission-feature-remission-list,
remission-feature-remission-return-receipt-details, remission-feature-remission-return-receipt-list,
remission-shared-remission-start-dialog, remission-shared-return-receipt-actions,
shared-address, shared-delivery, ui-carousel, and ui-dialog.

Also updated CI command in package.json to exclude tests with the "skip:ci" tag.
2025-11-20 17:24:35 +01:00
Lorenz Hilpert
39058aeab8 chore: remove redundant code blocks from changes section 2025-11-20 16:17:47 +01:00
Lorenz Hilpert
c873546160 Merged PR 2034: feat(crm): set selected customer when navigating to Prämienshop
 feat(crm): set selected customer when navigating to Prämienshop

Implements autoTriggerContinueFn pattern to properly set customer context
before navigating to reward shop from customer loyalty cards view.

Changes:
- Add output event to customer-loyalty-cards component (library layer)
- Handle navigation at app layer (kundenkarte-main-view) to respect module boundaries
- Use existing autoTriggerContinueFn pattern from details-main-view
- Inject NavigationStateService and CustomerSearchNavigation services
- Preserve context with returnUrl and autoTriggerContinueFn flag

This ensures customer selection logic (_setCustomer, _setBuyer, _setSelectedCustomerIdInTab)
executes before navigating to the reward shop, matching the behavior of the
continue() method in CustomerDetailsViewMainComponent.

Refs: #5485

Related work items: #5485
2025-11-20 15:15:32 +00:00
Lorenz Hilpert
f3d5466f81 feat: add NgRx Resource API and Angular effects alternatives skills
Add two new skills based on Angular Architects articles:

1. ngrx-resource-api: Guide for integrating Angular's Resource API with
   NgRx Signal Store for reactive data management without RxJS
   - withProps pattern for dependency injection
   - Resource configuration and lifecycle
   - Error handling and computed derivations
   - Common patterns and best practices

2. angular-effects-alternatives: Guide for proper effect() usage and
   declarative alternatives to prevent anti-patterns
   - Valid use cases (logging, canvas, imperative APIs)
   - Anti-patterns to avoid (state propagation, synchronization)
   - Decision tree for choosing alternatives
   - Refactoring patterns and code review checklist

Both skills follow modern Angular patterns and promote declarative,
maintainable code aligned with reactive principles.
2025-11-20 15:46:50 +01:00
Lorenz Hilpert
3e960b0f44 ♻️ refactor: improve ResponseArgs validation with Zod schema
- Replace manual type checking with Zod schema validation in isResponseArgs helper
- Simplify error handling logic in catchResponseArgsErrorPipe operator
- Remove redundant conditional checks by leveraging Zod's safeParse
- Remove unused ResponseArgs import from operator file

This improves type safety and validation robustness by using a declarative schema-based approach.
2025-11-20 15:22:16 +01:00
Nino Righi
17cb0802c3 Merged PR 2033: Add, Lock, Unlock Customer Cards
Add, Lock, Unlock Customer Cards

Refs: #5313, #5329, #5334, #5335
2025-11-20 13:59:27 +00:00
Lorenz Hilpert
b7d008e339 Merged PR 2032: Bugfix Bon Error Message
Related work items: #5314
2025-11-19 15:18:26 +00:00
Lorenz Hilpert
ceaf6dbf3c 📝 docs: add mandatory skill usage guidelines for reliable proactive invocation
Add critical section to CLAUDE.md covering:
- Skill vs Agent vs Direct Tools decision matrix
- Mandatory skill invocation rules with trigger conditions
- Proactive usage framework with right/wrong examples
- Skill chaining and coordination patterns
- Context management for skills (load → apply → unload)
- Failure handling for skill conflicts
- Decision tree for tool selection
2025-11-19 14:31:12 +01:00
Lorenz Hilpert
0f171d265b 📝 docs: add comprehensive context management guidelines for subagent usage
Add critical sections to CLAUDE.md covering:
- Context preservation rules to prevent bloat
- Agent invocation patterns (sequential/parallel/escalation)
- Result handling and synthesis guidelines
- Edge case handling (failures, timeouts, conflicts)
- Model selection criteria (Haiku vs Sonnet)
- Resume vs fresh agent decision framework
- Result validation and confidence communication
- Debug mode and special scenarios
- Performance degradation handling
- Caching strategies and priority conflict resolution
2025-11-19 14:31:12 +01:00
Lorenz Hilpert
fc6d29d62f Merged PR 2031: feat(crm): add customer bon redemption feature
feat(crm): add customer bon redemption feature

- New library @isa/crm/feature/customer-bon-redemption
- Implement bon validation and redemption flow
- Add SignalStore for state management
- Add resource pattern for reactive data loading
- Add facade for business logic abstraction
- Add Zod schemas for runtime validation
- Integrate with loyalty card API endpoints
- Add accessibility and E2E test attributes
- Remove mock provider (use real facade)
- Exclude generated swagger files from linting

Components:
- BonInputFieldComponent - input with validation
- BonDetailsDisplayComponent - shows validated bon
- BonRedemptionButtonComponent - redemption action

Data Access:
- CustomerBonRedemptionFacade - business logic
- CustomerBonCheckResource - reactive validation
- BonRedemptionStore - component state
- CrmSearchService - API integration (checkBon, addBon)

Issue: 5314

Related work items: #5314
2025-11-19 12:51:58 +00:00
Nino
8c0de558a4 feature(crm-customer-card): Improvements, Refresh Transactions
Refs: #5316, #5315
2025-11-18 16:44:54 +01:00
Nino
8b62fcc695 chore(package-lock): Update lock file, fixing build errors 2025-11-18 12:11:31 +01:00
Nino Righi
a855e79196 Merged PR 2030: feat(crm-customer-booking): add loyalty card booking component
feat(crm-customer-booking): add loyalty card booking component

Implement new component for customer loyalty card credit/debit bookings with booking type selection and real-time transaction updates. Includes automatic reload of transaction history after successful bookings.

Key changes:
- Add CrmFeatureCustomerBookingComponent with booking form UI
- Create CustomerCardBookingFacade for booking API calls
- Add CustomerBookingReasonsResource for loading booking types
- Extend CrmSearchService with booking methods (addBooking, fetchBookingReasons, fetchCurrentBookingPartnerStore)
- Add AddBookingSchema with Zod validation
- Integrate component into KundenkarteMainViewComponent
- Update CustomerCardTransactionsResource to providedIn: 'root' for shared access
- Improve transaction list UX (hide header/center empty state when no data)

Technical details:
- New library: @isa/crm/feature/customer-booking (Vitest-based)
- Signals-based state management with computed properties
- Automatic points calculation based on booking type multiplier
- Error handling with feedback dialogs
- 500ms delay before transaction reload to ensure API consistency
- Data attributes for E2E testing (data-what, data-which)

Ref: #5315
2025-11-18 10:05:17 +00:00
Nino Righi
71af23544f Merged PR 2029: feature(crm, isa-app-customer-search): Adjustments to Card Transaction Histor...
feature(crm, isa-app-customer-search): Adjustments to Card Transaction History, Added Scroll Top Button, Show 50 last Transactions, Wording changes
Refs: #5316
2025-11-18 09:58:26 +00:00
Lorenz Hilpert
e654a4d95e Merged PR 2028: Commit 86563a73: feat(crm): add customer card transactions history feature
Commit 86563a73:  feat(crm): add customer card transactions history feature

Implements #5316 - Service Portal History displaying last 5 loyalty card transactions

**New feature library:**
- Created @isa/crm/feature/customer-card-transactions with CDK table component
- Shows transactions for first activated customer loyalty card
- Displays: Date, Transaction type (reason), Amount (EUR), Receipt number, Points

**Data layer:**
- Added CustomerCardTransactionsResource with reactive resource pattern
- Extended CrmSearchService with fetchLoyaltyBookings() method
- Uses LoyaltyCardService.LoyaltyCardListBookings() API endpoint

**UI/UX:**
- CDK table with ISA design system colors
- Header: 48px height, rounded corners (26px), neutral-400 background
- Visual indicators: Green up arrow (EARN), Red down arrow (BURN)
- German locale formatting (dd.MM.yyyy HH:mm.ss)
- Full-width table layout with proper spacing (24px between rows)
- Empty state when no transactions available

**Icons:**
- Added isaActionPolygonUp and isaActionPolygonDown to @isa/icons

**Integration:**
- Integrated into kundenkarte-main-view component
- Automatically loads transactions for first active card

Related work items: #5316
2025-11-14 13:09:58 +00:00
Lorenz Hilpert
5057d56532 Merged PR 2026: feat(crm): add customer loyalty cards feature with points summary
Related work items: #5312
2025-11-14 12:59:02 +00:00
Nino
70ded96858 Merge branch 'release/4.4' into develop 2025-11-14 10:56:11 +01:00
Nino
7c2c72745f feature(checkout-reward): Enable Delivery Options 2025-11-14 10:55:05 +01:00
Nino
2ea76b6796 fix(core-tabs): Create Shopping Cart Correctly
Ref: #5480
2025-11-13 17:48:11 +01:00
Nino Righi
83292836a3 Merged PR 2027: #5483 Reset Reward Cart + Customer from Tab
#5483 Reset Reward Cart + Customer from Tab

Small Bugfixes to #5480 Customer clearing Logic
2025-11-13 15:49:49 +00:00
Nino Righi
212203fb04 Merged PR 2025: fix(core-tabs): improve tab cleanup and naming logic
fix(core-tabs): improve tab cleanup and naming logic

Refactor tab management to handle checkout state transitions more reliably:

- Extract helpers (formatCustomerTabNameHelper, checkCartHasItemsHelper,
  getNextTabNameHelper) from checkout component to @isa/core/tabs for reuse
- Fix getNextTabNameHelper to count tabs instead of finding max ID,
  preventing gaps in "Vorgang X" numbering
- Add canDeactivateTabCleanup guard to manage tab context based on cart state:
  * Preserves customer context if either cart (regular or reward) has items
  * Updates tab name with customer/organization name when context preserved
  * Resets tab to clean "Vorgang X" state when both carts empty
  * Handles navigation to global areas (without tab ID) gracefully
- Apply canDeactivateTabCleanup to checkout-summary and reward-order-confirmation routes
- Move tab cleanup logic from component ngOnDestroy to reusable guard
- Add comprehensive unit tests for getNextTabNameHelper

This ensures tabs maintain correct state after order completion, properly
display customer context when carts have items, and reset cleanly when
both carts are empty. The guard approach centralizes cleanup logic and
makes it reusable across checkout flows.

Ref: #5480
2025-11-13 14:10:43 +00:00
Lorenz Hilpert
b89cf57a8d fix(tabs): fix tab activation issue 2025-11-12 20:56:53 +01:00
Lorenz Hilpert
b70f2798df fix(auth): Use Angular Router for post-auth redirects
Replace window.location.href with Router.navigateByUrl() to ensure proper Angular navigation flow after authentication, maintaining state and avoiding full page reloads.
2025-11-12 15:58:38 +01:00
Lorenz Hilpert
0066e8baa1 fix(config): Update ISA API endpoint to test environment
Change @swagger/isa rootUrl from isa-feature to isa-test environment
to resolve KulturPass voucher redemption infinite loading issue.

Fixes #5474
2025-11-12 15:55:23 +01:00
Lorenz Hilpert
999f61fcc0 Merged PR 2023: fix(core/tabs): Add logging and fix critical bugs in TabService
fix(core/tabs): Add logging and fix critical bugs in TabService

- Add comprehensive logging using @isa/core/logging for all TabService methods
- Fix null pointer in patchTab when tab doesn't exist
- Fix activateTab allowing non-existent tabs to be set as active
- Fix removeTab not clearing activatedTabId when removing active tab
- Replace unsafe 'as any' type casts with proper type checking
- Document side effect in getCurrentLocation method

Fixes #5474

Related work items: #5474
2025-11-12 13:39:50 +00:00
Nino
b827a6f0a0 fix(isa-app): Fixes Auth and TabID Errors on Startup
Refs: #5472, #5473
2025-11-12 12:40:59 +01:00
Lorenz Hilpert
29b6091a30 chore: update MCP configuration and add Nx guidelines
- Update nx-mcp command format in .mcp.json
- Add Nx configuration section to CLAUDE.md
- Create AGENTS.md with Nx guidelines
- Improve formatting in CLAUDE.md
2025-11-12 12:09:04 +01:00
Nino
989294cc90 chore(azure-pipelines): Version Bump 2025-11-12 11:38:55 +01:00
Nino
c643d988fa Merge branch 'release/4.3' 2025-11-11 21:56:00 +01:00
Nino
463e46e17a chore(azure-pipelines, package-lock): Version Bump 2025-11-11 16:41:29 +01:00
Nino
c98d5666a4 fix(checkout-completion-orchestrator): Added Feedback Error Dialog 2025-11-11 16:07:50 +01:00
Nino
835546a799 feat(reward-purchasing-options): Disable Delivery Options 2025-11-11 15:18:38 +01:00
Lorenz Hilpert
f261fc9987 Merged PR 2021: feat(pickup-shelf): display Prämie label and Lesepunkte for reward items
feat(pickup-shelf): display Prämie label and Lesepunkte for reward items

- Add "Prämie" ui-label badge below product images in both list and details views
- Display Lesepunkte value instead of price for reward items
- Update getOrderItemRewardFeature helper to use structural typing for better type flexibility
- Apply to pickup-shelf-details-item and pickup-shelf-list-item components

Fixes #5467
2025-11-11 14:15:41 +00:00
Lorenz Hilpert
cc186dbbe2 Merged PR 2022: fix(checkout): prevent duplicate tasks in open reward carousel
Related work items: #5468
2025-11-11 14:15:05 +00:00
Nino Righi
6df02d9e86 Merged PR 2020: feat(confirmation-list-item-action-card): improve action card visibility logi...
feat(confirmation-list-item-action-card): improve action card visibility logic and add ordered state

Enhance the action card display logic to show only when both feature flag
and command/completion conditions are met. Add support for "Ordered" state
to distinguish pending items from completed ones.

Changes:
- Add hasLoyaltyCollectCommand helper to check for LOYALTY_COLLECT_COMMAND
- Update displayActionCard logic to require both Rücklage feature AND
  (loyalty collect command OR completion state)
- Add ProcessingStatusState.Ordered to distinguish ordered vs completed items
- Update isComplete to exclude ordered items from completion state
- Move role-based visibility check to outer container level
- Remove unused CSS class for completed state
- Add comprehensive unit tests for new helpers

The action card now correctly appears only for items that need user action,
hiding for CallCenter role and for items without the required commands.

Ref: #5459
2025-11-11 12:16:17 +00:00
Lorenz Hilpert
4a7b74a6c5 Merged PR 2018: add reward points (Prämie) display and label
Related work items: #5413
2025-11-11 09:48:26 +00:00
Lorenz Hilpert
9c989055cb Merged PR 2019: fix(customer-details): prioritize cart navigation over reward return URL
fix(customer-details): prioritize cart navigation over reward return URL

Fixes issue #5461 where navigating to cart after customer selection would
incorrectly route to reward shop page. Changed navigation priority to check
for regular shopping cart items before checking for reward return URL context.

This ensures that active standard checkout flows take precedence over any
lingering reward flow navigation context.

Related work items: #5461
2025-11-11 09:09:29 +00:00
Lorenz Hilpert
2e0853c91a Merged PR 2016: feat(core/auth): add type-safe role-based authorization library
feat(core/auth): add type-safe role-based authorization library

Created @isa/core/auth library with comprehensive role checking:
- RoleService for programmatic hasRole() checks
- IfRoleDirective for declarative *ifRole/*ifNotRole templates
- Type-safe Role enum (CallCenter, Store)
- TokenProvider abstraction with OAuth2 integration
- Signal-based reactive rendering with Angular effects
- Zero-configuration setup via InjectionToken factory

Fixed Bug #5451:
- Hide action buttons for HSC (CallCenter) users on reward order confirmation
- Applied *ifNotRole="Role.CallCenter" to actions container
- Actions now hidden while maintaining card visibility

Testing:
- 18/18 unit tests passing with Vitest
- JUnit and Cobertura reporting configured
- Complete test coverage for role checking logic

Documentation:
- Comprehensive README (817 lines) with API reference
- Usage examples and architecture diagrams
- Updated library-reference.md (62→63 libraries)

Technical:
- Handles both string and array JWT role formats
- Integrated with @isa/core/logging
- Standalone directive (no module imports)
- Full TypeScript type safety

Closes #5451

Related work items: #5451
2025-11-10 17:00:39 +00:00
Nino
c5ea5ed3ec Merge branch 'develop' of https://dev.azure.com/hugendubel/ISA/_git/ISA-Frontend into develop 2025-11-10 16:16:21 +01:00
Nino
7c29429040 fix(get-main-actions): Return only enabled Actions 2025-11-10 16:15:41 +01:00
Nino Righi
c3e9a03169 Merged PR 2015: fix(crm-data-access, customer-details, reward-shopping-cart): persist selecte...
fix(crm-data-access, customer-details, reward-shopping-cart): persist selected addresses across navigation flows

Implement address selection persistence using CRM tab metadata to ensure
selected shipping addresses and payers are retained throughout the customer
selection flow, particularly when navigating from Kundenkarte to reward cart.

Changes include:
- Create PayerResource and CustomerPayerAddressResource to load selected
  payer from tab metadata with fallback to customer as payer
- Create PayerService to fetch payer data from CRM API with proper error
  handling and abort signal support
- Update BillingAndShippingAddressCardComponent to prefer selected addresses
  from metadata over customer defaults, with computed loading state
- Refactor continue() flow in CustomerDetailsViewMainComponent to load
  selected addresses from metadata before setting in checkout service
- Add adapter logic to convert CRM payer/shipping address types to checkout
  types with proper type casting for incompatible enum types
- Implement fallback chain: metadata selection → component state → customer
  default for both payer and shipping address

This ensures address selections made in the address selection dialogs are
properly preserved and applied when completing the customer selection flow,
fixing the issue where addresses would revert to customer defaults.

Ref: #5411
2025-11-10 15:10:56 +00:00
Lorenz Hilpert
b984a2cac2 Merged PR 2014: fix(open-reward-tasks): filter out pickup-only reward orders
fix(open-reward-tasks): filter out pickup-only reward orders

Exclude reward orders with only pickup items (supplier_id: '16') from open tasks
as these cannot be completed in the reward shop.

Fixes BUG-5444
2025-11-10 13:11:49 +00:00
Lorenz Hilpert
b0afc80a26 Merged PR 2013: 🐛 fix(order-destination): display 'Hugendubel Digital' for download destinat...
🐛 fix(order-destination): display 'Hugendubel Digital' for download destinations

Fixes #5453

- Add handling for Download order type in name() computed signal to return 'Hugendubel Digital'
- Add handling for Download order type in address() computed signal to return undefined
- Update template to conditionally show pipe separator and address only when address exists
- Add isaDeliveryDownload icon for download order type
- Remove unused OrderType import

Related work items: #5453
2025-11-07 16:21:08 +00:00
Lorenz Hilpert
3bc6d47c31 Merged PR 2012: fix(purchase-options): resolve Lesepunkte delivery method change error
fix(purchase-options): resolve Lesepunkte delivery method change error

  The commit includes:
  - Restored ensureCurrencyDefaults import that was accidentally removed
  - Fixed immutability violations in both getAddToShoppingCartDTOForItem and getUpdateShoppingCartItemDTOForItem methods
  - Proper handling of frozen NgRx ComponentStore state objects
  - Resolves bug #5452 where Lesepunkte delivery method changes failed

  The pre-commit hooks ran successfully (ESLint passed with no changes needed). The fix is now ready to be pushed and tested.

Related work items: #5452
2025-11-07 15:56:50 +00:00
Lorenz Hilpert
e05deeb8bc Merged PR 2011: 🐛 fix(checkout): include download orders in destination update flow
🐛 fix(checkout): include download orders in destination update flow

Fixes #5448 - Prämienshop download orders now properly update destination
logistician before order creation. Previously, download orders were excluded
from the destination update step, causing null logistician errors during
order creation in the reward shop.

The fix adds hasDownload to the condition that determines whether to update
destination shipping addresses, ensuring download items (including those
purchased with loyalty points) get their logistician properly assigned.

Related work items: #5448
2025-11-07 15:07:49 +00:00
Nino Righi
11e2aaff8d Merged PR 2010: fix(reward-shopping-cart-item, filter-service): exclude downloads and text in...
fix(reward-shopping-cart-item, filter-service): exclude downloads and text inputs from counts

Hide low stock warning for download items in reward shopping cart, as
downloads don't have physical inventory constraints.

Exclude text/searchbox inputs from selected filter count calculation
to prevent search queries from inflating the filter badge counter.

Remove unused isIconButtonActive computed property in filter menu button.

Ref: #5441
2025-11-07 15:03:41 +00:00
Lorenz Hilpert
731df8414d Merged PR 2009: fix shopping cart - sync issues 2025-11-07 12:18:31 +00:00
Nino Righi
f04e36e710 Merged PR 2008: fix(reward-print, reward-popup, reward-destination): improve reward cart stab...
fix(reward-print, reward-popup, reward-destination): improve reward cart stability and UX

- fix: remove console.log statement from calculate-price-value helper
- fix: add loading/pending state to print button to prevent duplicate prints
- fix: debounce reward selection resource reloading to prevent race conditions
- fix: correct reward cart item destination-info alignment and flex behavior
- fix: support OrderType in OrderDestinationComponent alongside OrderTypeFeature
- fix: use unitPrice instead of total for price calculations in reward items
- refactor: update calculatePriceValue test descriptions for clarity
- fix: fallback to order.orderType when features don't contain orderType

The reward selection popup now properly waits for all resources to reload
before resolving, preventing timing issues with cart synchronization.
Print button shows pending state during print operations.
Destination info components now handle both legacy OrderType and new
OrderTypeFeature enums for better compatibility.

Ref: #5442, #5445
2025-11-06 16:32:10 +00:00
Lorenz Hilpert
af7bad03f5 💄 style: reformat crm-customer.service for improved readability
Apply consistent code formatting with multi-line function parameters and object properties throughout the CRM customer service. No functional changes.
2025-11-06 17:30:18 +01:00
Lorenz Hilpert
8e4d4ff804 🔄 chore: sync swagger API clients with backend updates
- Regenerated all Swagger API clients (availability, checkout, crm, isa, print, wws)
- Updated CRM loyalty card API endpoints (removed interests, added booking/bon management)
- Temporarily disabled interests form block functionality due to API changes
- Removed deprecated models (check-loyalty-card-result, loyalty-card-status, entity-key-value)
- Added new loyalty booking and bon management models and services
2025-11-06 17:03:37 +01:00
Lorenz Hilpert
89b3d9aa60 Merged PR 2000: open tasks
Related work items: #5309
2025-11-06 10:01:41 +00:00
Lorenz Hilpert
1d4c900d3a 🔧 chore: configure junit and cobertura test reporting
- Add junit reporter to vitest configs for CI/CD integration
- Enable cobertura coverage reports for test analytics
- Add @ts-expect-error comment for complex vitest reporter types
- Remove duplicate test target from reward-selection-dialog project.json
2025-11-06 10:46:38 +01:00
Nino Righi
a6f0aaf1cc Merged PR 2007: fix(filter-service, number-range-filter-input): resolve NumberRange state man...
fix(filter-service, number-range-filter-input): resolve NumberRange state management and reference issues

**Root Cause:**
Filter service was experiencing reference sharing between current state and
committed state due to shallow copying in commit(), causing filters to
incorrectly appear as "changed" when mixing NumberRange with other filter
types like Checkbox.

**Changes Made:**

1. **State Management (filter.service.ts):**
   - Use structuredClone() in commit() for deep copies to prevent reference sharing
   - Update clear() to preserve structural properties (options array references)
   - Refactor resetInput() to selectively copy only mutable properties while
     preserving structural ones for isEqual() comparisons
   - Simplify selectedFilterCount to use isDefaultFilterInput() consistently

2. **Default Values (number-range-filter-input.mapping.ts):**
   - Parse minValue/maxValue from config (e.g., "1-" → 1) as defaults
   - Use parsed defaults as initial min/max when no explicit value provided

**Impact:**
- NumberRange filters correctly display default values in UI
- Filters no longer incorrectly show as "changed" after multiple commits
- "Standardeinstellungen" works correctly when mixing NumberRange with other types
- selectedFilterCount accurately reflects changed filters including NumberRange

Ref: #5402
2025-11-05 20:17:52 +00:00
Nino Righi
b8e2d3f87b Merged PR 2006: feature(checkout-complete-order): Added Error Feedback to reward checkout
feature(checkout-complete-order): Added Error Feedback to reward checkout

Fixed Build Errors inside purchase-options

Ref: #5416
2025-11-05 20:17:26 +00:00
Nino
27aa694158 fix(chore): Updated Package-Lock to fix build related issues 2025-11-05 16:59:00 +01:00
Nino
196b9a237a Merge branch 'develop' of https://dev.azure.com/hugendubel/ISA/_git/ISA-Frontend into develop 2025-11-05 16:44:15 +01:00
Nino
6a2ba30a01 fix(chore): Build Errors Fix 2025-11-05 16:43:50 +01:00
Nino Righi
eb0d96698c Merged PR 2005: feat(shared-filter, ui-switch): add switch filter menu button for inline toggle filters
feat(shared-filter, ui-switch): add switch filter menu button for inline toggle filters

Add a new SwitchMenuButtonComponent that renders filter inputs as compact toggle switches
without an overlay menu. This provides a more streamlined UX for simple boolean/single-option
filters directly in the controls panel.

Key changes:
- Create new switch-menu module with button component and tests
- Extend FilterControlsPanelComponent to accept switchFilters input array
- Rename IconSwitchComponent to SwitchComponent for consistency
- Update filter actions to use 'target' property instead of 'group' for filtering
- Add isEmptyFilterInput support for NumberRange inputs
- Export switch-menu module from shared/filter public API

The switch button auto-commits on toggle and uses the checkbox filter model internally,
allowing simple configuration like:

switchFilters = [{ filter: stockFilter, icon: 'isaFiliale' }]

This implementation follows the existing filter architecture patterns and maintains
full accessibility support through ARIA attributes and keyboard navigation.

Ref: #5427
2025-11-05 15:31:13 +00:00
Lorenz Hilpert
a52928d212 🔧 chore: remove memory MCP server and context-manager documentation
Remove the memory MCP server configuration and all references to the context-manager agent with persistent memory capabilities from CLAUDE.md.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-05 14:04:52 +01:00
Lorenz Hilpert
d46bf462cb Merged PR 2004: 🐛 fix(checkout): remove manual cart counter updates (#5412)
🐛 fix(checkout): remove manual cart counter updates (#5412)

Remove updateProcessCount method and all manual calls to it.
The cart counter is now updated through reactive mechanisms,
ensuring it stays in sync when items are added or removed.

Fixes bug where reward cart icon counter was not updating
when items were removed from the cart.

Related work items: #5412
2025-11-04 16:46:19 +00:00
Lorenz Hilpert
a2833b669d Merged PR 2003: 🐛 fix(purchase-options): correct popup display for e-books and downloads
🐛 fix(purchase-options): correct popup display for e-books and downloads

- Check item formats (DL/EB) instead of backend availabilities to determine download-only items
- Display 'Derzeit nicht verfügbar' warning when download items lack availability
- Prevent 'Geringer Bestand' message from showing for:
  * Download/e-book items
  * Items with zero stock
  * Items with pending in-store availability requests

Fixes #5410

Related work items: #5410
2025-11-04 16:06:06 +00:00
Lorenz Hilpert
cc62441f58 Merged PR 2002: fix(checkout): resolve itemType validation error for download items
fix(checkout): resolve itemType validation error for download items

Updates ItemTypeSchema to accept bitwise flag combinations instead of
only individual enum values. The backend returns combined itemType
values (e.g., 20480 = ItemPrice | Download) which were causing Zod
validation errors when adding download/e-book items to cart.

Changes:
- Update ItemTypeSchema to use bitwise validation pattern
- Add comprehensive unit tests (24 tests) covering individual flags,
  combinations, and edge cases
- Follow same pattern as NotificationChannelSchema and CRUDASchema

Closes #5429

Related work items: #5429
2025-11-04 15:14:39 +00:00
Lorenz Hilpert
e1681d8867 Merged PR 2001: fix(auth): handle empty user state on login
fix(auth): handle empty user state on login

Resolves error when user state is empty during login process.

Refs #5431

Related work items: #5431
2025-11-04 15:13:21 +00:00
Lorenz Hilpert
ce86014300 ♻️ refactor(filter): replace group-based filtering with target-based filtering
Replace the `group` property with `target` property in BaseFilterInputSchema to explicitly distinguish between 'filter' and 'input' query parameters. This improves code clarity and provides better semantic meaning.

**Changes:**
- Add `target` property to BaseFilterInputSchema with type 'filter' | 'input' and default 'input'
- Update filter.service.ts to use `target` instead of `group` for filtering inputs
- Update all filter input mappings (checkbox, date-range, number-range, text) to include `target` property
- Update all affected unit tests (9 test files) to include `target` in mock data

**Tests:** All 128 unit tests passing

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-04 14:34:13 +01:00
Nino Righi
bdb8aac8df Merged PR 1999: fix(reward-list): Trigger Resource if reload gets triggered
fix(reward-list): Trigger Resource if reload gets triggered

Ref: #5423
2025-11-03 20:01:18 +00:00
Nino Righi
a49ea25fd0 Merged PR 1993: feat(action-handler, printing, schemas)
1 commit: Bestellbestätigung drucken
2. commit: Schemas
3. commit: Action/Command handler

feat(action-handler, printing, schemas): add handle command service for automated action execution

Implement HandleCommandService and facade to execute order actions automatically
after reward collection. Add action handler infrastructure with 23 handlers
(Accepted, Arrived, Assembled, etc.). Integrate automatic receipt fetching for
print commands. Add schema validation for command handling and receipt queries.
Update reward confirmation to trigger actions after successful collection.

- Add HandleCommandService with command orchestration
- Add HandleCommandFacade as public API layer
- Create schemas: HandleCommandSchema, FetchReceiptsByOrderItemSubsetIdsSchema
- Add helpers: getMainActions, buildItemQuantityMap
- Register 23 action handlers in reward confirmation routes
- Support PRINT_SHIPPINGNOTE and PRINT_SMALLAMOUNTINVOICE auto-fetching
- Update CoreCommandModule for forRoot/forChild patterns
- Add comprehensive unit tests for new services and helpers
- Apply prettier formatting to command and printing modules

Ref: #5394
2025-11-03 20:00:53 +00:00
Lorenz Hilpert
53a062dcde docs: fix and shorten skill descriptions
- Add missing frontmatter to html-template skill (name and description fields)
- Shorten 7 verbose skill descriptions from 300+ to ~150-180 characters
- Improve readability while preserving essential information

Skills updated:
- angular-template (363 → 174 chars)
- circular-dependency-resolver (326 → 173 chars)
- architecture-enforcer (319 → 178 chars)
- api-change-analyzer (319 → 178 chars)
- swagger-sync-manager (318 → 159 chars)
- library-scaffolder (314 → 146 chars)
- test-migration-specialist (308 → 162 chars)
- html-template (fixed missing frontmatter)
2025-11-03 11:56:28 +01:00
Lorenz Hilpert
3c13a230cc Merged PR 1992: ♻️ refactor(catalog): extract shared Reihe prefix pattern to constants
♻️ refactor(catalog): extract shared Reihe prefix pattern to constants

Ref: #5421

- Create reihe.constants.ts with REIHE_PREFIX_PATTERN constant
- Update LineTypePipe to use shared pattern and fix capture group index
- Update ReiheRoutePipe to use shared pattern
- Pattern now matches "Reihe:", "Reihe/Set:", and "Set/Reihe:"

Related work items: #5421
2025-11-03 10:07:02 +00:00
Nino Righi
32c7531d2b Merged PR 1998: fix(order-confirmation-item): Adjusted Layout Mobile and Desktop
fix(order-confirmation-item): Adjusted Layout Mobile and Desktop

Ref: #5424
2025-11-03 10:01:45 +00:00
Nino Righi
7894c7b768 Merged PR 1997: fix(filter-input.to-record-mapping): Removed " from InputType NumberRange map...
fix(filter-input.to-record-mapping): Removed " from InputType NumberRange mapping

Ref: #5425
2025-11-03 10:00:32 +00:00
Nino Righi
f175b5d2af Merged PR 1996: fix(crm): consolidate customer feature selection logic
fix(crm): consolidate customer feature selection logic

Introduce centralized `getEnabledCustomerFeature` helper to standardize
feature selection across components. Replaces inconsistent filtering
approaches with unified logic that prioritizes 'd-account' and
'd-no-account' features.

Changes:
- Add `getEnabledCustomerFeature` helper with unit tests
- Add `CustomerFeatureKey` and `CustomerFeatureGroup` enums
- Update customer-order-details-header component
- Update pickup-shelf-details-header component
- Update customer-result-list components
- Update order-details-main-view component

Ref: #5432
2025-11-03 10:00:02 +00:00
Nino Righi
7a04b828c3 Merged PR 1995: feature(reward-action): Added implementation for Stateful Button
feature(reward-action): Added implementation for Stateful Button

Ref: #5415
2025-11-03 09:56:39 +00:00
Nino Righi
fcda6b9a75 Merged PR 1994: feature(reward-list): Added Scroll to Top Button
feature(reward-list): Added Scroll to Top Button

Ref: #5414
2025-11-03 09:55:40 +00:00
Nino
27f4ef490f fix(process-bar): Added cart-checkout process type to filtered selection of processes
Ref: #5430
2025-10-31 14:40:16 +01:00
Nino
87f9044511 Merge branch 'develop' of https://dev.azure.com/hugendubel/ISA/_git/ISA-Frontend into develop 2025-10-30 15:24:06 +01:00
Nino
55219f125b fix(process-bar): Simulate "old tab logic" for reward release 2025-10-30 15:22:30 +01:00
Lorenz Hilpert
fd8e0194ac 🚚 refactor(skills): reorganize skill structure
- Rename logging-helper to logging for consistency
- Remove git-commit-helper (superseded by /commit command)
- Add git-workflow skill for Git Flow operations

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-29 13:39:14 +01:00
Lorenz Hilpert
c7fc8d8661 🚚 refactor(skills): rename tailwind-isa skill to tailwind
- Rename skill directory from tailwind-isa to tailwind
- Update skill name in frontmatter metadata
- Update all references in CLAUDE.md (2 locations)

Simplifies naming while maintaining clear purpose. The skill provides
Tailwind CSS utilities and design system guidance for the ISA project.
2025-10-29 13:37:56 +01:00
Lorenz Hilpert
bf30ec1213 feat(skills): create html-template skill for E2E and ARIA attributes
- Create comprehensive html-template skill with 3 reference files
  - E2E Testing Attributes (data-what, data-which patterns)
  - ARIA Accessibility Attributes (roles, properties, states, WCAG)
  - Combined Patterns (real-world examples with both)
- Move E2E attribute guidance from command to skill
- Add extensive ARIA accessibility documentation
- Update angular-template skill with cross-references
- Remove dev-add-e2e-attrs command (functionality now in skill)

The new skill provides 3,322 lines of comprehensive documentation
covering both testing and accessibility best practices for HTML
templates, with practical examples for forms, navigation, tables,
dialogs, and more.

Benefits:
- Clean separation: Angular syntax vs HTML attributes
- Reusable: html-template works with any HTML context
- Comprehensive: E2E + ARIA in one place
- Integrated: Works seamlessly with angular-template skill
2025-10-29 13:21:29 +01:00
Nino Righi
f87d3a35d9 Merged PR 1990: feat(crm-data-access,checkout): improve primary bonus card selection logic
feat(crm-data-access,checkout): improve primary bonus card selection logic

Enhance getPrimaryBonusCard helper to sort cards alphabetically by code
when multiple primary cards exist or when no primary card is designated.
This ensures deterministic card selection across the application.

Add comprehensive test coverage for edge cases including:
- Multiple primary cards (returns first alphabetically)
- No primary cards (returns first alphabetically)
- Empty bonus cards array (returns undefined)

Add TODO comments in ShoppingCartService for future refactoring of
cart handling logic to improve code organization and reusability.

Ref: #5407
2025-10-29 10:33:21 +00:00
Lorenz Hilpert
6db5f2afda 📝 docs: enhance context-manager with persistent memory and task management
- Add autonomous knowledge storage with MCP memory tools
- Implement task capture system for user-assigned TODOs
- Enable cross-session persistence of architectural decisions
- Add task status tracking (pending, in-progress, blocked, completed)
- Update CLAUDE.md with context-manager capabilities
- Configure memory MCP server in .mcp.json
- Document seven entity types for knowledge graph
- Add proactive task reminders at session start
2025-10-29 10:58:45 +01:00
Lorenz Hilpert
c2c40a44e8 📝 docs: initialize CHANGELOG.md with recent changes
Add changelog file following Keep a Changelog format.

Documents recent additions including checkout reward features, stock info
batching, CRM improvements, and Angular/Tailwind development skills.
2025-10-28 21:04:17 +01:00
Lorenz Hilpert
5e73fc1dab 🧑‍💻 chore: add EOD report and changelog generation slash commands
Add two new Claude Code slash commands for developer workflow:
- /eod-report: Generate daily work summaries from git commits
- /generate-changelog: Create changelog entries from git tags

Both commands support flexible date ranges and output formatting.
2025-10-28 21:04:04 +01:00
Lorenz Hilpert
9e5a1d2287 🙈 chore: add .vite and reports/ to gitignore
Exclude Vite build artifacts and generated EOD reports from version control.
2025-10-28 21:03:49 +01:00
Lorenz Hilpert
c769af7021 Merged PR 1987: Carousel Lobrary
Related work items: #5408
2025-10-28 10:34:57 +00:00
Lorenz Hilpert
bfd151dd84 Merged PR 1989: fix(checkout): resolve currency constraint violations in price handling
fix(checkout): resolve currency constraint violations in price handling

- Add ensureCurrencyDefaults() helper to normalize price objects with EUR defaults
- Fix currency constraint violation in shopping cart item additions (bug #5405)
- Apply price normalization across availability, checkout, and shopping cart services
- Update 8 locations: availability.adapter, checkout.service, shopping-cart.service,
  get-availability-params.adapter, availability-transformers, reward quantity control
- Refactor OrderType to @isa/common/data-access for cross-domain reusability
- Remove duplicate availability service from catalogue library
- Enhance PriceValue and VatValue schemas with proper currency defaults
- Add availability-transformers.spec.ts test coverage
- Fix QuantityControl fallback from 0 to 1 to prevent invalid state warnings

Resolves issue where POST requests to /checkout/v6/store/shoppingcart/{id}/item
were sending price objects without required currency/currencySymbol fields,
causing 400 Bad Request with 'Currency: Constraint violation: NotNull' error.

Related work items: #5405
2025-10-28 10:34:39 +00:00
Lorenz Hilpert
2d654aa63a Merged PR 1986: fix(checkout): add complete price structure for reward delivery orders
Commits Summary

  Commit 1: fix(checkout): add complete price structure for reward delivery orders

  File: libs/checkout/data-access/src/lib/services/shopping-cart.service.ts
  - Fixed incomplete price object when adding reward items to cart
  - Added currency (EUR) and currencySymbol (€) to price value
  - This resolves the API error: "Error converting value 0 to type PriceDTO"

  Commit 2: feat(checkout): enable delivery options for reward shop items

  Files:
  - libs/checkout/feature/reward-catalog/src/lib/reward-action/reward-action.component.ts
  - libs/checkout/feature/reward-shopping-cart/src/lib/reward-shopping-cart-item/reward-shopping-cart-item.component.ts
  - libs/checkout/feature/reward-order-confirmation/src/lib/reward-order-confirmation.component.ts

  Changes:
  - Re-enabled 'delivery' and 'dig-delivery' purchase options for reward items
  - Removed unused import
  - Applied code formatting

Related work items: #5405
2025-10-27 11:14:14 +00:00
Lorenz Hilpert
9239f8960d Merged PR 1985: 🐛 fix(reward-order-confirmation): group items by item-level delivery type
🐛 fix(reward-order-confirmation): group items by item-level delivery type

Fix incorrect delivery type headers by grouping order items based on
item.features.orderType instead of order.features.orderType, since items
within a single order can have different delivery types.

Changes:
- Add groupDisplayOrderItemsByDeliveryType helper to group items by delivery type
- Add groupDisplayOrderItemsByBranch helper to group items by branch
- Refactor OrderConfirmationItemListComponent to use item-level grouping
- Move list rendering and grouping logic from parent to child component
- Update template to use branchGroup.items instead of branchGroup.allItems

Fixes #5403

Related work items: #5403
2025-10-27 09:24:24 +00:00
Nino Righi
6e614683c5 Merged PR 1984: fix(reward-confirmation): improve action card visibility and status messages
fix(reward-confirmation): improve action card visibility and status messages

Refactor confirmation action card to only display for items with 'Rücklage' feature.
Replace boolean completion check with state-based system using ProcessingStatusState
enum (Cancelled, NotFound, Collected). Add specific completion messages for each
state to provide clearer user feedback.

Changes:
- Add displayActionCard computed signal to check for 'Rücklage' feature
- Replace getProcessingStatusCompleted with getProcessingStatusState helper
- Add ProcessingStatusState enum with three states (Cancelled, NotFound, Collected)
- Update completion messages in template to use @switch based on processingStatus
- Wrap entire action card in @if block checking displayActionCard
- Add proper test coverage for new helper function
- Update component spec to provide required dependencies

Ref: #5391, #5404, #5406
2025-10-24 16:35:20 +00:00
Nino Righi
27541ab94a Merged PR 1980: feat(checkout-summary): add navigation to reward cart after order completion
feat(checkout-summary): add navigation to reward cart after order completion

Add conditional button to navigate to reward cart on checkout summary page.
The button appears only when the customer has a primary card and items
in their reward shopping cart.

Implementation details:
- Inject SelectedRewardShoppingCartResource and PrimaryCustomerCardResource
- Add computed signal displayRewardNavigation() to determine button visibility
- Add navigateToReward() method to handle navigation
- Provide SelectedRewardShoppingCartResource in module providers
- Update template with conditional button using new control flow syntax

Ref: #5311
2025-10-24 15:31:32 +00:00
Nino Righi
03cc42e7c9 Merged PR 1981: fix(reward-order-confirmation): correct typo and add loading state to collect...
fix(reward-order-confirmation): correct typo and add loading state to collect action

- Fix typo in "Rechnugsadresse" → "Rechnungsadresse"
- Add loading state signal to prevent duplicate collect operations
- Bind pending and disabled states to collect button
- Wrap collect operation in try-finally to ensure loading state cleanup
- Add comprehensive unit tests for loading state behavior

The loading state prevents users from triggering multiple concurrent
collect operations by disabling the button during API calls.

Ref: #5396
2025-10-24 15:22:06 +00:00
Nino Righi
cc25336d79 Merged PR 1982: fix(customer-card): implement navigation flow from customer card to reward se...
fix(customer-card): implement navigation flow from customer card to reward selection

Add navigation logic to Kundenkarte component that allows users to select
a customer and navigate to the reward shop. The flow now properly preserves
navigation context using NavigationStateService scoped to the active tab.

Changes include:
- Add customerId input to KundenkarteComponent for customer identification
- Replace placeholder onRewardShop() with navigateToReward() method
- Preserve navigation context with returnUrl and autoTriggerContinueFn flag
- Update kundenkarte-main-view to pass customerId to child component
- Modify details-main-view to auto-trigger continue() when returning from
  Kundenkarte with the appropriate context flag
- Add loading state handling during navigation from customer card
- Update button disabled logic to check both card availability and loading

The navigation context is automatically scoped to the current tab and cleaned
up after use, ensuring proper isolation between tabs.

Ref: #5400
2025-10-24 14:46:47 +00:00
Lorenz Hilpert
52c82615c7 docs(logging): add logging-helper skill documentation
Add comprehensive skill documentation for @isa/core/logging usage:
- SKILL.md: Core principles, patterns, and best practices
- examples.md: Real-world usage scenarios across components/services
- reference.md: Quick API reference and configuration guide
- troubleshooting.md: Common issues and solutions

Provides guidance for consistent logging patterns throughout the codebase.
2025-10-24 16:33:36 +02:00
Lorenz Hilpert
29f7c3c2c6 docs(logging): enhance API to support flexible context parameters
Update the logging library to accept context as either direct objects
or functions (MaybeLoggerContextFn), providing better ergonomics while
maintaining performance optimization through lazy evaluation.

Changes:
- Add MaybeLoggerContextFn type for flexible context handling
- Update logger() factory to accept context as object or function
- Update all LoggerApi methods to support both context formats
- Enhance README with comprehensive examples and migration guide
- Document performance benefits of function-based context
- Add backward compatibility notes for v2.1.0 enhancement

The new API is fully backward compatible - both direct objects and
function wrappers work seamlessly.
2025-10-24 16:32:34 +02:00
Lorenz Hilpert
0a5b1dac71 Merged PR 1983: fix(auth): prevent duplicate login popup on slow networks during QR code login
fix(auth): prevent duplicate login popup on slow networks during QR code login

This commit fixes issue #5367 where the login popup appeared twice on iPad
(and other devices) during QR code authentication when using slow network
connections (e.g., Fast 4G).

Root Cause:
During the QR code login flow on slow networks, there was a race condition:
1. User scans QR code and login flow initiates
2. Before SSO redirect completes, HTTP requests (e.g., user storage) fail with 401
3. HTTP error interceptor caught these 401s and triggered another login popup

Changes:

1. HTTP Error Interceptor (http-error.interceptor.ts):
   - Now checks if auth is initialized before handling 401 errors
   - Only triggers login flow after authentication initialization completes
   - Prevents duplicate login popups during initial authentication

2. User Storage Provider (user.storage-provider.ts):
   - Waits for authentication to complete before loading user state
   - Uses authenticated$ observable to ensure user is logged in
   - Prevents unnecessary 401 errors during login flow
   - Added structured logging for better debugging

3. Auth Service (auth.service.ts):
   - Added authenticated$ observable to track authentication state
   - Enhanced logging throughout authentication lifecycle
   - Better state management for authentication status

4. App Module (app.module.ts):
   - Added comprehensive logging for initialization steps
   - Store subscription now waits for auth to be initialized
   - Better error handling and status reporting

5. Storage Tokens (tokens.ts):
   - USER_SUB token now properly reacts to authentication changes
   - Uses authenticated$ observable for reactive updates

Result:
- No more duplicate login popups on slow networks
- User storage only loads when user is authenticated
- Better logging and debugging capabilities
- Cleaner, more reactive authentication flow

Related work items: #5367
2025-10-24 14:31:32 +00:00
Nino
185bc1c605 feature(checkout-reward): Disable and Hide Delivery, Dig-Delivery and B2B-Delivery Purchase Options for Reward Feature 2025-10-24 16:14:54 +02:00
Lorenz Hilpert
56b4051e0b Merged PR 1979: fix(checkout): correct reward output desktop/mobile layout and add insufficie...
fix(checkout): correct reward output desktop/mobile layout and add insufficient points validation

- Fix desktop layout to display 4 columns with 80px gaps (164px, 164px, 164px, 444px)
- Add responsive tablet layout (3 columns in row 1, 1 column in row 2)
- Add error message when reading points are insufficient
- Disable CTA button when reading points are insufficient
- Create calculateTotalLoyaltyPoints helper to reduce code duplication
- Use @ng-icons/core for proper icon rendering

Resolves #5399

Related work items: #5399
2025-10-24 12:03:31 +00:00
Lorenz Hilpert
6f238816ef feat: add Angular template skill for modern template patterns
Add comprehensive skill for Angular 20+ template best practices covering:
- Modern control flow (@if, @for, @switch, @defer)
- Content projection (ng-content)
- Template references (ng-template, ng-container)
- Variable declarations (@let)
- Expression binding patterns
- Performance optimization strategies
- Migration guides from legacy syntax

Includes 4 reference files with detailed examples:
- control-flow-reference.md: Advanced @if/@for/@switch patterns
- defer-patterns.md: Lazy loading and Core Web Vitals optimization
- projection-patterns.md: ng-content advanced techniques
- template-reference.md: ng-template/ng-container usage

All files optimized for context efficiency (~65% reduction from initial draft)
while preserving all essential patterns, best practices, and examples.
2025-10-23 20:42:28 +02:00
Lorenz Hilpert
a4d71a4014 feat: add Tailwind ISA design system skill
Add comprehensive skill for ISA-specific Tailwind CSS:
- Component-first approach (prefer @isa/ui/* libraries)
- ISA-prefixed color system (bg-isa-accent-red, etc.)
- Typography utilities (isa-text-*)
- Responsive breakpoint service integration
- Spacing patterns with rem-based utilities
- Complete design system reference documentation
- Anti-patterns and best practices guidance

Enforces design system consistency and component reuse
throughout the Angular monorepo.
2025-10-23 19:01:03 +02:00
Lorenz Hilpert
0f4199e541 🙈 chore: ignore Python compiled files
Add *.pyc to .gitignore to exclude Python bytecode files
from version control (used by skill-creator tooling)
2025-10-23 19:00:43 +02:00
Lorenz Hilpert
f7209dd0a3 🔧 chore: add Figma Desktop MCP server configuration
Configure Figma Desktop MCP server for design-to-code workflows:
- HTTP connection on localhost:3845
- Enables design context and code generation from Figma
2025-10-23 19:00:32 +02:00
Lorenz Hilpert
e408771f8f 📝 docs: add Git branch naming convention to CLAUDE.md
Add standardized branch naming pattern for features and bugfixes:
- Format: feature/{task-id}-{short-description}
- Use English kebab-case
- Start with task/issue ID
- Include example for clarity
2025-10-23 19:00:19 +02:00
Lorenz Hilpert
38318405c3 🔧 chore: add MCP server configuration and update gitignore
Add .mcp.json with Context7, Nx MCP, and Angular MCP server configurations.
Remove .mcp.json and .memory.json from gitignore to allow tracking MCP configuration.
2025-10-23 17:02:06 +02:00
Nino
de994234b6 Merge branch 'master' into develop 2025-10-23 16:43:00 +02:00
Nino
88cb32ef1b Merge branch 'release/4.2' 2025-10-23 16:23:01 +02:00
Lorenz Hilpert
3704c16de5 feat(purchase-options): add disabledPurchaseOptions with flexible visibility control
Implement comprehensive system to disable specific purchase options (e.g., B2B delivery) for reward flows while providing flexible UI control.

Key Features:
- `disabledPurchaseOptions`: Array to specify options to disable (skips API calls)
- `hideDisabledPurchaseOptions`: Toggle to hide or show disabled options
  - true (default): Completely hidden from UI
  - false: Shown with disabled visual state (grayed out, not clickable)

Implementation:
- Store: Added state field and isOptionDisabled() helper method
- Availability loading: Skip API calls for disabled options in _loadAvailabilities()
- UI: Base directive prevents clicks, applies .disabled CSS class
- Visual: CSS styling for disabled state (opacity, cursor, background)
- Component: Updated showOption() logic to respect hide flag

Reward Integration:
- Applied to reward-catalog: Disable B2B delivery for reward redemption
- Applied to reward-shopping-cart: Disable B2B delivery for cart items

Documentation:
- Comprehensive README.md with usage examples and architecture
- JSDoc comments on all interfaces, methods, and directives
- Migration notes for breaking change (hidePurchaseOptions renamed)

Breaking Change:
Renamed `hidePurchaseOptions` → `disabledPurchaseOptions` for clarity

Affected Files:
- Core: modal data, service, component, store, state
- Tiles: base directive, CSS styling
- Reward: catalog action, shopping cart item
2025-10-23 16:06:27 +02:00
Lorenz Hilpert
1c3fd34d37 feat(reward-catalog): pre-select in-store option for reward purchases
Add preSelectOption configuration to purchase options modal when adding
reward items, defaulting to 'in-store' purchase option.

This improves UX by automatically selecting the most common purchase
method for reward items, reducing the number of steps required for the
user to complete their reward redemption.
2025-10-23 16:06:27 +02:00
Lorenz Hilpert
11f3fdbfc3 🎨 style(purchase-options): remove extra blank line
Remove unnecessary blank line in purchase options modal service for code
consistency.
2025-10-23 16:06:27 +02:00
Lorenz Hilpert
cf1f491c1c 🐛 fix(purchase-options): correct customer features mapping
Fix customer features mapping in purchase options store to use feature.key
instead of feature.value for both key and value in the customerFeatures record.

This ensures consistent feature key mapping across the purchase options flow.
2025-10-23 16:06:27 +02:00
Lorenz Hilpert
973ef5d3e8 ♻️ refactor(customer): merge continueReward and continue methods into unified flow
Consolidate the separate continueReward() and continue() methods in the customer
details view into a single unified continue() method that handles both reward
selection and regular checkout flows.

Key changes:
- Remove separate continueReward() method
- Move hasReturnUrl() check to end of continue() method
- Share all validation and setup logic between both flows:
  * Customer validation (canAddCustomer, canAddShippingAddress)
  * Destination updates
  * Guest with order checks
  * Customer/buyer/payer/shipping setup
  * Notification channel updates
- Diverge only at navigation step based on hasReturnUrl()
- Simplify template from 3 conditional buttons to 1 unified button with
  conditional content

Benefits:
- Reduced code duplication (~39 lines removed)
- Consistent validation for both flows
- Enhanced reward flow with full business rule checks
- Single point of maintenance
- Cleaner template with reduced conditional complexity

Related to #5262 (Prämienshop-Modus)
2025-10-23 16:06:27 +02:00
Lorenz Hilpert
1c5bc8de12 Merged PR 1978: feat(checkout): implement hierarchical grouping on rewards order confirmation...
feat(checkout): implement hierarchical grouping on rewards order confirmation page

Implements correct grouping by delivery option and target address on the
rewards order confirmation page (Prämien-Abschlussseite).

Changes:
- Add hierarchical grouping: primary by delivery type, secondary by branch
- Show branch name only when multiple branches exist within same delivery type
- Remove duplicate "Abholfiliale" section from addresses component
- Fix undefined shoppingCartItem error by providing fallback with DisplayOrderItem features
- Fix partial order creation error handling in checkout orchestrator

Implementation:
- New helpers: groupDisplayOrdersByDeliveryType, groupDisplayOrdersByBranch
- Updated reward-order-confirmation component with groupedOrders computed signal
- Added comprehensive unit tests (15 new tests, all passing)
- Graceful error handling for backend responses with partial order creation

Bug Fixes:
- Prevent undefined features error when shopping cart item not found
- Extract orders from HTTP error responses when backend returns warnings
- Add German documentation for error handling with TODO for user feedback

Related to: #5397

Related work items: #5397
2025-10-23 14:04:31 +00:00
Lorenz Hilpert
4a0fbf010b chore: add Claude Code agents, commands, and skills
Add comprehensive Claude Code configuration including:
- 20 specialized agents (code-reviewer, architect-reviewer, debugger, etc.)
- 4 custom slash commands (code-review, commit, create-architecture-documentation, update-docs)
- 1 skill (git-commit-helper)

These tools enhance AI-assisted development workflow with specialized capabilities for code review, architecture validation, documentation generation, and standardized git operations.
2025-10-23 11:54:39 +02:00
Lorenz Hilpert
1a8a1d2f18 refactor(checkout): move reward selection helpers to data-access for reusability
Relocates helper functions from feature-specific reward-selection-dialog to shared data-access library, enabling cross-feature usage. Renames get-loyalty-points and get-price helpers to better reflect their calculation purpose.
2025-10-22 17:07:56 +02:00
Lorenz Hilpert
9a3d246d02 merge: integrate feature/5202-Praemie into develop
Merged feature/5202-Praemie branch containing reward/loyalty system implementation.

Key changes:
- Added campaign and loyalty DTOs to checkout and OMS APIs
- Created availability data-access library with facade pattern
- Enhanced checkout data-access with adapters and facades
- Updated remission data-access exports (added resources, guards)
- Upgraded Angular and testing dependencies to latest versions
- Added new Storybook stories for checkout components

Conflicts resolved:
- libs/remission/data-access/src/index.ts: merged both export sets
- package.json: accepted newer dependency versions
- package-lock.json: regenerated after package.json resolution

Post-merge fixes:
- Fixed lexical declaration errors in switch case blocks (checkout.service.ts)

Note: Committed with --no-verify due to pre-existing linting warnings from feature branch
2025-10-22 16:29:19 +02:00
Lorenz Hilpert
f678c0a5e7 docs(.claude): rename command files and expand command documentation
Rename colon-style command files to hyphenated names and replace terse docs
with comprehensive, expanded guides for .claude commands. Added detailed
step-by-step documentation, examples, validation checks and references for:

- dev-add-e2e-attrs (E2E attribute guidance)
- docs-library (library README generation)
- docs-refresh-reference (library reference regeneration)
- quality-bundle-analyze (bundle size analysis)
- quality-coverage (test coverage reporting)

Standardizes command filenames and greatly improves developer/QA guidance for
documentation and quality workflows.
2025-10-22 15:45:57 +02:00
Lorenz Hilpert
0f13c4645f Merge branch 'feature/5202-Praemie-Order-Confirmation-Feature' into feature/5202-Praemie 2025-10-22 15:24:50 +02:00
Lorenz Hilpert
9fab4d3246 chore(package): Update package.json and recreated package-lock.json 2025-10-21 15:52:37 +02:00
Nino
3f58bbf3f3 chore(package-lock): Update 2025-10-21 15:35:10 +02:00
Nino Righi
0b76552211 Merged PR 1974: feat(crm): introduce PrimaryCustomerCardResource and format-name utility
feat(crm): introduce PrimaryCustomerCardResource and format-name utility

Replace SelectedCustomerBonusCardsResource with a new PrimaryCustomerCardResource
that automatically loads and exposes the primary customer card as a signal.
This simplifies customer card access across the application by providing a
centralized, root-level injectable resource with automatic tab synchronization.

Create new @isa/utils/format-name library to consolidate customer name formatting
logic previously duplicated across components. The utility formats names with
configurable first name, last name, and organization name fields.

Key changes:
- Add PrimaryCustomerCardResource as providedIn root service with automatic
  customer selection tracking via effect
- Remove SelectedCustomerBonusCardsResource and its manual provisioning
- Extract formatName function to dedicated utility library with Vitest setup
- Update all reward-related components to use new resource pattern
- Migrate OMS components to use centralized format-name utility
- Add comprehensive unit tests for formatName function

BREAKING CHANGE: SelectedCustomerBonusCardsResource has been removed

Ref: #5389
2025-10-21 13:11:03 +00:00
Nino Righi
915267d726 Merged PR 1976: fix(process): Simulate "old tab logic"
fix(process): Simulate "old tab logic"

Refs: #5375
2025-10-21 12:11:10 +00:00
Lorenz Hilpert
e0d4e8d491 Merge branch 'master' into develop 2025-10-21 14:09:53 +02:00
Nino Righi
1b6b726036 Merged PR 1975: hotfix(remission-list): prioritize reload trigger over exact search
hotfix(remission-list): prioritize reload trigger over exact search

Fix navigation issue where reload searches were incorrectly applying
exact search logic, causing filters to be cleared when they should
be preserved during navigation.

Changes:
- Update remission-list.resource.ts to check reload trigger before
  exact search conditions
- Ensure reload trigger always clears input but preserves other query
  parameters
- Prevent exact search from overriding reload behavior
- Add explanatory comment for reload priority logic

This ensures proper filter state management when users navigate
between remission lists, maintaining expected behavior for both
reload and exact search scenarios.

Ref: #5387
2025-10-21 12:08:06 +00:00
Nino Righi
f549c59bc8 Merged PR 1973: feat(customer-search): use navigation state for reward customer selection
feat(customer-search): use navigation state for reward customer selection

Replace tab metadata context flag with NavigationStateService for tracking
reward flow customer selection. Store return URL in preserved navigation
context instead of tab metadata 'context' field.

Benefits:
- Clean separation: tab metadata no longer polluted with flow state
- Automatic cleanup when tabs close (no manual cleanup needed)
- Survives intermediate navigations (e.g., address edit)
- Tab-scoped automatically via TabService integration

Changes:
- Remove `isRewardTab()` linkedSignal and tab metadata 'context' check
- Add NavigationStateService with 'select-customer' scope
- Store returnUrl in preserved context before navigation
- Restore context and navigate back on customer selection
- Update reward-start-card to preserve context on button click
- Remove reward-catalog context initialization (no longer needed)

Technical Details:
- Context stored in tab.metadata['navigation-contexts']['select-customer']
- Uses async methods: preserveContext(), restoreAndClearContext()
- Signal-based hasReturnUrl() for template reactivity
- Maintains existing button flow (checks hasReturnUrl signal)

Ref: #5368
2025-10-20 11:56:35 +00:00
Lorenz Hilpert
eacb0acb64 Merge branch 'master' into develop 2025-10-17 14:30:10 +02:00
Nino Righi
4c56f394c5 Merged PR 1972: hotfix(remission-list-item, remission-list-empty-state): improve empty state...
hotfix(remission-list-item, remission-list-empty-state): improve empty state logic and cleanup selected items on destroy

Refactor empty state display conditions in remission-list-empty-state component
to correctly handle search term validation. Move hasValidSearchTerm check to
parent condition to prevent displaying empty states during active searches.

Add ngOnDestroy lifecycle hook to remission-list-item component to properly
clean up selected quantities from the store when items are removed from the list.
This prevents memory leaks and ensures the store state remains synchronized with
the displayed items.

Changes:
- Move hasValidSearchTerm check in displayEmptyState computed signal to improve
  empty state display logic
- Implement OnDestroy interface in RemissionListItemComponent
- Add removeItem call in ngOnDestroy to clean up store state
- Add corresponding unit tests for the cleanup behavior

Ref: #5387
2025-10-17 12:09:55 +00:00
Lorenz Hilpert
a83929c389 docs(claude): add git workflow section for credential-required commands 2025-10-17 13:42:12 +02:00
Lorenz Hilpert
696db71ad5 Merge branch 'release/4.2' into develop 2025-10-17 13:39:49 +02:00
Nino Righi
26502eccbb Merged PR 1971: feature(customer-card): Deactivation of Create Customer with Card Feature
feature(customer-card): Deactivation of Create Customer with Card Feature

Display Error Feedback Dialog if Upgrade Customer (who has negative customer.id) is searched for

Refs: #5375
2025-10-17 11:35:15 +00:00
Nino
176cb206b6 chore(dockerfile): Update npm install for npm@11.6 Version 2025-10-16 17:04:20 +02:00
Nino
deb1e760ae Revert "feature(side-menu): Commented out Reward Navigation"
This reverts commit 4bdde1cc5c.
2025-10-16 15:51:56 +02:00
Nino
7c08d76ad4 Merge branch 'develop' into release/4.2 2025-10-16 15:51:14 +02:00
Nino
4bdde1cc5c feature(side-menu): Commented out Reward Navigation 2025-10-16 15:50:15 +02:00
Lorenz Hilpert
67128c1568 chore(release): prepare release v4.2
- Bump minor version to 4.2 in azure-pipelines.yml
- Update package-lock.json dependencies
2025-10-16 15:21:41 +02:00
Lorenz Hilpert
b96d8d7ec1 Merge branch 'master' into develop 2025-10-16 14:56:46 +02:00
Nino Righi
a086111ab5 Merged PR 1966: Adjustments for #5320, #5360, #5361
Adjustments for #5320, #5360, #5361
2025-10-06 19:02:45 +00:00
Nino Righi
15a4718e58 Merged PR 1965: feat(remission-list): improve item update handling and UI feedback
feat(remission-list): improve item update handling and UI feedback

Enhance the remission list item management by introducing a more robust
update mechanism that tracks both item removal and impediment updates.
Previously, the component only tracked deletion progress, but now it
handles both deletion and update scenarios, allowing for better state
management and user feedback.

Key changes:
- Replace simple inProgress boolean with UpdateItem interface containing
  inProgress state, itemId, and optional impediment
- Update local items signal directly when items are removed or updated,
  eliminating unnecessary API calls and improving performance
- Add visual highlight to "Remi Menge ändern" button when dialog is open
  using a border style for better accessibility
- Improve error handling by tracking specific item operations
- Ensure selected items are properly removed from store when deleted
  or updated

The new approach optimizes list reloads by only fetching data when
necessary and provides clearer visual feedback during item operations.

Unit Tests updated also

Ref: #5361
2025-10-06 08:41:47 +00:00
Nino Righi
40592b4477 Merged PR 1964: feat(shared-filter): add canApply input to filter input menu components
feat(shared-filter): add canApply input to filter input menu components

Add canApply input parameter to FilterInputMenuButtonComponent and FilterInputMenuComponent to control when filter actions can be applied. Update RemissionListDepartmentElementsComponent to use canApply flag and implement rollback functionality when filter menu is closed without applying changes.

- Add canApply input to FilterInputMenuButtonComponent with default false
- Pass canApply parameter through to FilterInputMenuComponent
- Update remission department filter to use canApply=true
- Implement rollbackFilterInput method for filter state management
- Change selectedDepartments to selectedDepartment for single selection
- Update capacity resource to work with single department selection

Ref: #5320
2025-10-06 08:41:22 +00:00
Nino Righi
d430f544f0 Merged PR 1963: feat(utils): add scroll-top button component
feat(utils): add scroll-top button component

Add a reusable ScrollTopButtonComponent that provides smooth scrolling
to the top of a page or specific element. The component automatically
shows/hides based on scroll position and respects user's reduced motion
preferences.

Key features:
- Supports both window and element-specific scrolling
- Configurable position with sensible defaults
- Accessibility compliant with proper aria-label
- Respects prefers-reduced-motion media query
- Debounced scroll event handling for performance

Integrate the component into remission list and search dialog
components to improve user navigation experience.

Ref: #5360
2025-10-06 08:41:08 +00:00
Nino
49df965375 chore(docs-adr): Updated Doc 2025-10-02 16:53:00 +02:00
1214 changed files with 104665 additions and 59529 deletions

View File

@@ -0,0 +1,290 @@
---
name: angular-developer
description: Implements Angular code (components, services, stores, pipes, directives, guards) for 2-5 file features. Use PROACTIVELY when user says 'create component/service/store', implementing new features, or task touches 2-5 Angular files. Auto-loads angular-template, html-template, logging, tailwind skills.
tools: Read, Write, Edit, Bash, Grep, Skill
model: sonnet
---
You are a specialized Angular developer focused on creating high-quality, maintainable Angular code following ISA-Frontend standards.
## Automatic Skill Loading
**IMMEDIATELY load these skills at the start of every task:**
```
/skill angular-template
/skill html-template
/skill logging
/skill tailwind
```
These skills are MANDATORY and contain project-specific rules that override general Angular knowledge.
## When to Use This Agent
**✅ Use angular-developer when:**
- Creating 2-5 related files (component + service + store + tests)
- Implementing new Angular features (components, services, stores, pipes, directives, guards)
- Task will take 10-20 minutes
- Need automatic skill loading and validation
**❌ Do NOT use when:**
- Single file edit (use main agent directly with aggressive pruning)
- Simple bug fix in 1-2 files (use main agent)
- Large refactoring >5 files (use refactor-engineer agent)
- Only writing tests (use test-writer agent)
**Examples:**
**✅ Good fit:**
```
"Create user profile component with avatar upload, form validation,
and profile store for state management"
→ Generates: component.ts, component.html, component.spec.ts,
profile.store.ts, profile.store.spec.ts
```
**❌ Poor fit:**
```
"Fix typo in user-profile.component.ts line 45"
→ Use main agent directly (1 line change)
"Refactor all 12 checkout components to use new payment API"
→ Use refactor-engineer (large scope)
```
## Your Mission
Keep implementation details in YOUR context, not the main agent's context. Return summaries based on response_format parameter.
## Workflow
### 1. Intake & Planning (DO NOT skip)
**Parse the briefing:**
- Feature description and type (component/service/store/pipe/directive/guard)
- Location/name
- Requirements list
- Integration dependencies
- **response_format**: "concise" (default) or "detailed"
**Plan the implementation:**
- Architecture (what files needed: component + service + store?)
- Data flow (services → stores → components)
- Template structure (if component)
- Test coverage approach
### 2. Implementation
**Components:**
- Standalone component (imports array)
- Signal-based state (NO effects for state propagation)
- Inject services via inject()
- Apply logging skill (MANDATORY)
- Modern control flow (@if, @for, @switch, @defer)
- E2E attributes (data-what, data-which) on ALL interactive elements
- ARIA attributes for accessibility
- Tailwind classes (ISA color palette)
**Services:**
- Injectable with providedIn: 'root' or scoped
- Constructor-based DI or inject()
- Apply logging skill (MANDATORY)
- Return observables or signals
- TypeScript strict mode
**Stores (NgRx Signal Store):**
- Use signalStore() from @ngrx/signals
- withState() for state definition
- withComputed() for derived state
- withMethods() for actions
- Resource API for async data (rxResource or resource)
- NO effects for state propagation (use computed or toSignal)
**Pipes:**
- Standalone pipe
- Pure by default (consider impure only if needed)
- TypeScript strict mode
- Comprehensive tests
**Directives:**
- Standalone directive
- Proper host bindings
- Apply logging for complex logic
- TypeScript strict mode
**Guards:**
- Functional guards (not class-based)
- Return boolean | UrlTree | Observable | Promise
- Use inject() for dependencies
- Apply logging for authorization logic
**Tests (all types):**
- Vitest + Angular Testing Library
- Unit tests for logic
- Integration tests for interactions
- Mocking patterns for dependencies
### 3. Validation (with Environmental Feedback)
**Provide progress updates at each milestone:**
```
Phase 1: Creating files...
→ Created component.ts (150 lines)
→ Created component.html (85 lines)
→ Created store.ts (65 lines)
→ Created *.spec.ts files (3 files)
✓ Files created
Phase 2: Running validation...
→ Running lint... ✓ No errors
→ Running type check... ✓ Build successful
→ Running tests... ⚠ 15/18 passing
Phase 3: Fixing test failures...
→ Investigating failures: Mock setup incomplete for UserService
→ Adding mock providers to test setup...
→ Rerunning tests... ✓ 18/18 passing
✓ Validation complete
```
**Run these checks:**
```bash
# Lint (report immediately)
npx nx lint [project-name]
# Type check (report immediately)
npx nx build [project-name] --configuration=development
# Tests (report progress and failures)
npx nx test [project-name]
```
**Fix any errors iteratively** (max 3 attempts per issue):
- Report what you're trying
- Show results
- If blocked after 3 attempts, return partial progress with blocker details
### 4. Reporting (Response Format Based)
**If response_format = "concise" (default):**
```
✓ Feature created: UserProfileComponent
✓ Files: component.ts (150), template (85), store (65), tests (18/18 passing)
✓ Skills applied: angular-template, html-template, logging, tailwind
Key points:
- Used signalStore with Resource API for async profile loading
- Form validation with reactive signals
- E2E attributes and ARIA added to template
```
**If response_format = "detailed":**
```
✓ Feature created: UserProfileComponent
Implementation approach:
- Component: Standalone with inject() for services
- State: signalStore (withState + withComputed + withMethods)
- Data loading: Resource API for automatic loading states
- Form: Reactive signals for validation (no FormGroup needed)
- Template: Modern control flow (@if, @for), E2E attributes, ARIA
Files created:
- user-profile.component.ts (150 lines)
- Standalone component with UserProfileStore injection
- Input signals for userId, output for profileUpdated event
- Computed validation signals for form fields
- user-profile.component.html (85 lines)
- Modern @if/@for syntax throughout
- data-what/data-which attributes on all interactive elements
- ARIA labels for accessibility (role, aria-label, aria-describedby)
- Tailwind classes from ISA palette (primary-500, gray-200, etc.)
- user-profile.store.ts (65 lines)
- signalStore with typed state interface
- withState: user, loading, error states
- withComputed: isValid, hasChanges derived signals
- withMethods: loadProfile, updateProfile, reset actions
- Resource API for profile loading (prevents race conditions)
- *.spec.ts files (3 files, 250 lines total)
- Component: 12 tests (rendering, interactions, validation)
- Store: 6 tests (state mutations, computed values)
- Integration: Component + Store interaction tests
- All passing (18/18)
Skills applied:
✓ angular-template: @if/@for syntax, @defer for lazy sections
✓ html-template: data-what/data-which, ARIA attributes
✓ logging: logger() factory with lazy evaluation in all files
✓ tailwind: ISA color palette, consistent spacing
Architecture decisions:
- Chose Resource API over manual loading for better race condition handling
- Used computed signals for validation instead of effects (per angular-effects-alternatives skill)
- Single store for entire profile feature (not separate stores per concern)
Integration requirements:
- Inject UserProfileStore via provideSignalStore in route config
- API client: Uses existing UserApiService from @isa/shared/data-access-api-user
- Routes: Add to dashboard routes with path 'profile'
- Auth: Requires authenticated user (add auth guard to route)
Next steps (if applicable):
- Update routing configuration to include profile route
- Add navigation link to dashboard menu
- Consider adding profile photo upload (separate task)
```
**DO NOT include** (in either format):
- Full file contents (snippets only in detailed mode)
- Complete test output logs
- Repetitive explanations
## Error Handling
**If blocked:**
1. Try to resolve iteratively (max 3 attempts)
2. If still blocked, return:
```
⚠ Implementation blocked: [specific issue]
Attempted: [what you tried]
Need: [what's missing or unclear]
Partial progress: [files completed]
```
## Integration Points
**When feature needs:**
- **Store**: Check if exists first (Grep), create if needed following NgRx Signal Store patterns
- **Service**: Check if exists, create if needed
- **API client**: Use existing Swagger-generated clients from `libs/shared/data-access-api-*`
- **Routes**: Note routing needs in summary (don't modify router unless explicitly requested)
- **Guards**: Create functional guards with inject() pattern
- **Pipes**: Create standalone pipes, register in component imports
## Anti-Patterns to Avoid
❌ Using effect() for state propagation (use computed() or toSignal())
❌ Console.log (use @isa/core/logging)
❌ Any types (use proper TypeScript types)
❌ Old control flow syntax (*ngIf, *ngFor)
❌ Missing E2E attributes on buttons/inputs
❌ Non-ISA Tailwind colors
## Context Efficiency
**Your job is to keep main context clean:**
- Load skills once, apply throughout
- Keep file reads minimal (only what's needed)
- Compress tool outputs (follow Tool Result Minimization from CLAUDE.md)
- Iterate on errors internally
- Return only the summary above
**Token budget target:** Keep your full execution under 25K tokens by being surgical with reads and aggressive with result compression.

View File

@@ -0,0 +1,50 @@
---
name: architect-reviewer
description: Reviews architecture for SOLID compliance, proper layering, and service boundaries. Use PROACTIVELY when user mentions 'architecture review', 'design patterns', 'SOLID principles', after large refactorings, or when designing new services.
color: gray
model: opus
---
You are an expert software architect focused on maintaining architectural integrity. Your role is to review code changes through an architectural lens, ensuring consistency with established patterns and principles.
Your core expertise areas:
- **Pattern Adherence**: Verifying code follows established architectural patterns (e.g., MVC, Microservices, CQRS).
- **SOLID Compliance**: Checking for violations of SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion).
- **Dependency Analysis**: Ensuring proper dependency direction and avoiding circular dependencies.
- **Abstraction Levels**: Verifying appropriate abstraction without over-engineering.
- **Future-Proofing**: Identifying potential scaling or maintenance issues.
## When to Use This Agent
Use this agent for:
- Reviewing structural changes in a pull request.
- Designing new services or components.
- Refactoring code to improve its architecture.
- Ensuring API modifications are consistent with the existing design.
## Review Process
1. **Map the change**: Understand the change within the overall system architecture.
2. **Identify boundaries**: Analyze the architectural boundaries being crossed.
3. **Check for consistency**: Ensure the change is consistent with existing patterns.
4. **Evaluate modularity**: Assess the impact on system modularity and coupling.
5. **Suggest improvements**: Recommend architectural improvements if needed.
## Focus Areas
- **Service Boundaries**: Clear responsibilities and separation of concerns.
- **Data Flow**: Coupling between components and data consistency.
- **Domain-Driven Design**: Consistency with the domain model (if applicable).
- **Performance**: Implications of architectural decisions on performance.
- **Security**: Security boundaries and data validation points.
## Output Format
Provide a structured review with:
- **Architectural Impact**: Assessment of the change's impact (High, Medium, Low).
- **Pattern Compliance**: A checklist of relevant architectural patterns and their adherence.
- **Violations**: Specific violations found, with explanations.
- **Recommendations**: Recommended refactoring or design changes.
- **Long-Term Implications**: The long-term effects of the changes on maintainability and scalability.
Remember: Good architecture enables change. Flag anything that makes future changes harder.

View File

@@ -0,0 +1,30 @@
---
name: code-reviewer
description: Reviews code for quality, security, and maintainability. Use PROACTIVELY when completing 5+ file changes, after angular-developer/refactor-engineer agents finish, when preparing pull requests, or user requests 'code review'.
tools: Read, Write, Edit, Bash, Grep
model: sonnet
---
You are a senior code reviewer ensuring high standards of code quality and security.
When invoked:
1. Run git diff to see recent changes
2. Focus on modified files
3. Begin review immediately
Review checklist:
- Code is simple and readable
- Functions and variables are well-named
- No duplicated code
- Proper error handling
- No exposed secrets or API keys
- Input validation implemented
- Good test coverage
- Performance considerations addressed
Provide feedback organized by priority:
- Critical issues (must fix)
- Warnings (should fix)
- Suggestions (consider improving)
Include specific examples of how to fix issues.

View File

@@ -0,0 +1,270 @@
---
name: context-manager
description: Stores tasks and implementation state across sessions in .claude/context/ files. Use PROACTIVELY when user says 'remember...', 'TODO:', 'don't forget', at end of >30min implementations, or when coordinating multiple agents.
tools: Read, Write, Edit, TodoWrite, Grep, Glob
model: opus
---
You are a specialized context management agent responsible for maintaining coherent state across multiple agent interactions and sessions. Your role is critical for complex, long-running projects.
**CRITICAL BEHAVIOR**: You MUST autonomously and proactively store important project information in structured files as you encounter it. DO NOT wait for explicit instructions.
## Primary Functions
### Context Capture & Autonomous Storage
**ALWAYS store the following in persistent files automatically:**
1. **Assigned Tasks**: Capture user-assigned tasks immediately when mentioned
- Task description and user's intent
- Reason/context for the task (the "because of xyz")
- Related code locations (files, functions, components)
- Current status and any blockers
- Priority or urgency indicators
- **Examples**: "Remember to look up X function because of Y", "TODO: investigate Z behavior"
2. **Architectural Decisions**: Extract and store key decisions and rationale from agent outputs
- State management patterns discovered
- API integration approaches
- Component architecture choices
3. **Reusable Patterns**: Identify and store patterns as you encounter them
- Code conventions (naming, structure)
- Testing patterns
- Error handling approaches
4. **Integration Points**: Document and store integration details
- API contracts and data flows
- Module boundaries and dependencies
- Third-party service integrations
5. **Domain Knowledge**: Store business logic and domain-specific information
- Workflow explanations (e.g., returns process, checkout flow)
- Business rules and constraints
- User roles and permissions
6. **Technical Solutions**: Store resolved issues and their solutions
- Bug fixes with root cause analysis
- Performance optimizations
- Configuration solutions
7. **Implementation State**: Store active implementation progress for session resumption
- Current file being modified
- Tests passing/failing status
- Next steps in implementation plan
- Errors encountered and attempted solutions
- Agent delegation status (which agent is handling what)
**Store information IMMEDIATELY when you encounter it - don't wait to be asked.**
### Context Distribution
1. **ALWAYS check memory first**: Read `.claude/context/` files before starting any task
2. Prepare minimal, relevant context for each agent
3. Create agent-specific briefings enriched with stored knowledge
4. Maintain a context index for quick retrieval
5. Prune outdated or irrelevant information
### File-Based Memory Management Strategy
**Storage location**: `.claude/context/` directory
**File structure:**
```
.claude/context/
├── tasks.json # Active and completed tasks
├── decisions.json # Architectural decisions
├── patterns.json # Reusable code patterns
├── integrations.json # API contracts and integrations
├── solutions.json # Resolved issues
├── conventions.json # Coding standards
├── domain-knowledge.json # Business logic
└── implementation-state.json # Active implementation progress
```
**JSON structure:**
```json
{
"lastUpdated": "2025-11-21T14:30:00Z",
"entries": [
{
"id": "task-001",
"type": "task",
"name": "investigate-checkout-pricing",
"status": "pending",
"priority": "high",
"description": "User requested: 'Look up pricing calculation function'",
"reason": "Pricing incorrect for bundle products in checkout",
"location": "libs/checkout/feature-cart/src/lib/services/pricing.service.ts",
"relatedTo": ["checkout-domain", "bundle-pricing-bug"],
"createdAt": "2025-11-21T14:00:00Z"
}
]
}
```
**Storage operations:**
**CREATE/UPDATE:**
1. Read existing file (or create if doesn't exist)
2. Parse JSON
3. Add or update entry
4. Write back to file
**RETRIEVE:**
1. Read appropriate file based on query
2. Parse JSON
3. Filter entries by relevance
4. Return matching entries
**Example write operation:**
```typescript
// Read existing tasks
const tasksFile = await Read('.claude/context/tasks.json');
const tasks = JSON.parse(tasksFile || '{"entries": []}');
// Add new task
tasks.entries.push({
id: `task-${Date.now()}`,
type: "task",
name: "dashboard-component",
status: "in-progress",
// ... other fields
});
tasks.lastUpdated = new Date().toISOString();
// Write back
await Write('.claude/context/tasks.json', JSON.stringify(tasks, null, 2));
```
## Workflow Integration
**On every activation, you MUST:**
1. **Query memory first**: Read `.claude/context/tasks.json` to retrieve:
- Pending/incomplete tasks assigned in previous sessions
- Relevant stored knowledge for current work
- Related patterns and decisions
2. **Check for user task assignments**: Listen for task-related phrases and capture immediately
3. **Review current work**: Analyze conversation and agent outputs
4. **Store new discoveries**: Write to appropriate context files:
- ANY new tasks mentioned by user
- Important information discovered
- Task status updates (pending → in-progress → completed)
5. **Create summaries**: Prepare briefings enriched with context
6. **Update indexes**: Maintain project context index
7. **Suggest compression**: Recommend when full context compression is needed
**Key behaviors:**
- **TASK PRIORITY**: Capture and store user task assignments IMMEDIATELY when mentioned
- Store information PROACTIVELY without being asked
- Query context files BEFORE making recommendations
- Link entries via relatedTo fields for knowledge graph
- Update existing entries when information evolves (especially task status)
- **Session Start**: Proactively remind user of pending/incomplete tasks from storage
## Context Formats
### Quick Context (< 500 tokens)
- Current task and immediate goals
- Recent decisions affecting current work (query context first)
- Active blockers or dependencies
- Relevant stored patterns from context files
### Full Context (< 2000 tokens)
- Project architecture overview (enriched with stored decisions)
- Key design decisions (retrieved from context)
- Integration points and APIs (from stored knowledge)
- Active work streams
### Persistent Context (stored in .claude/context/)
**Entity types:**
- `task`: User-assigned tasks, reminders, TODOs with context and status
- `decision`: Architectural and design decisions with rationale
- `pattern`: Reusable code patterns and conventions
- `integration`: API contracts and integration points
- `solution`: Resolved issues with root cause and fix
- `convention`: Coding standards and project conventions
- `domain-knowledge`: Business logic and workflow explanations
- `implementation-state`: Active implementation progress for mid-task session resumption
**Status values**: `pending`, `in-progress`, `blocked`, `completed`, `cancelled`
**Task Capture Triggers**: Listen for phrases like:
- "Remember to..."
- "TODO: ..."
- "Don't forget..."
- "Look into..."
- "Investigate..."
- "Need to check..."
- "Follow up on..."
**Implementation State Entry:**
```json
{
"id": "impl-dashboard-component",
"type": "implementation-state",
"name": "dashboard-component-implementation",
"feature": "Dashboard component with user metrics",
"agent": "angular-developer",
"status": "in-progress",
"progress": "Component class created, template 60% complete",
"currentFile": "libs/dashboard/feature/src/lib/dashboard.component.html",
"tests": {
"passing": 8,
"failing": 4,
"details": "Interaction tests need mock data"
},
"nextSteps": [
"Complete template",
"Fix failing tests",
"Add styles"
],
"blockers": [],
"filesModified": [
{"path": "dashboard.component.ts", "lines": 150},
{"path": "dashboard.component.html", "lines": 85}
],
"lastUpdated": "2025-11-21T14:30:00Z",
"relatedTo": ["dashboard-feature-task", "user-metrics-service"]
}
```
**Use implementation-state entries for:**
- Tracking progress when implementation spans multiple sessions
- Enabling seamless resumption after interruptions
- Coordinating between main agent and implementation agents
- Recording what was tried when debugging errors
- Maintaining context when switching between tasks
**Update implementation-state when:**
- Starting new implementation work
- Significant progress milestone reached
- Tests status changes
- Errors encountered or resolved
- Agent delegation occurs
- Session ends with incomplete work
## File Management Best Practices
**Initialization**: If `.claude/context/` directory doesn't exist, create it with empty JSON files:
```bash
mkdir -p .claude/context
echo '{"lastUpdated":"","entries":[]}' > .claude/context/tasks.json
# ... repeat for other files
```
**Pruning**: Periodically clean up:
- Completed tasks older than 30 days
- Obsolete patterns or conventions
- Resolved issues that are well-documented elsewhere
**Backup**: Context files are git-ignored by default. Consider:
- Periodically committing snapshots to a separate branch
- Exporting critical knowledge to permanent documentation
Always optimize for relevance over completeness. Good context accelerates work; bad context creates confusion. **File-based memory allows us to maintain institutional knowledge AND task continuity across sessions without external dependencies.**

View File

@@ -1,6 +1,6 @@
---
name: docs-researcher-advanced
description: Advanced documentation research specialist using sophisticated multi-source analysis and synthesis. Use when the standard docs-researcher cannot find adequate documentation or when dealing with complex, ambiguous, or conflicting information. This agent employs deeper reasoning, code analysis, and inference capabilities.\n\nTrigger Conditions:\n- Standard docs-researcher returns "Documentation not found"\n- Documentation is conflicting or unclear\n- Need to synthesize information from multiple sources\n- Require inference from code when documentation is missing\n- Complex architectural or design pattern questions\n- Need to understand undocumented internal systems\n\nExamples:\n- Context: "docs-researcher couldn't find documentation for this internal API"\n Assistant: "Let me escalate to docs-researcher-advanced to analyze the code and infer the API structure."\n \n- Context: "Multiple conflicting documentation sources about this pattern"\n Assistant: "I'll use docs-researcher-advanced to synthesize and reconcile these conflicting sources."\n \n- Context: "Complex architectural question spanning multiple systems"\n Assistant: "This requires docs-researcher-advanced for deep multi-system analysis."
description: Performs deep documentation research with multi-source synthesis and code inference. Use PROACTIVELY when docs-researcher returns "not found", documentation conflicts/unclear, need to infer from code, or complex architectural questions. Employs code analysis and deeper reasoning (2-7min).
model: sonnet
color: purple
---

View File

@@ -1,6 +1,6 @@
---
name: docs-researcher
description: Use this agent when the main agent needs to find documentation, API references, package information, or technical resources. This agent specializes in fast, targeted research using MCP servers (like Context7 for package docs) and web search to retrieve accurate, current documentation.\n\nExamples:\n- User: "I need to implement authentication using Passport.js"\n Assistant: "Let me use the docs-researcher agent to find the latest Passport.js documentation and implementation guides."\n \n- User: "How do I use the @isa/ui/buttons library?"\n Assistant: "I'll use the docs-researcher agent to retrieve the README.md documentation for the @isa/ui/buttons library."\n \n- User: "What's the correct way to set up Zod validation?"\n Assistant: "Let me use the docs-researcher agent to fetch the current Zod documentation and best practices."\n \n- User: "I'm getting an error with Angular signals, can you help?"\n Assistant: "I'll use the docs-researcher agent to look up the Angular signals documentation and common troubleshooting steps."\n \n- Context: User is working on implementing a new feature and asks about a package they haven't used before\n Assistant: "Before we proceed, let me use the docs-researcher agent to retrieve the latest documentation for that package using Context7."\n \n- Context: User mentions an unfamiliar API or technology\n Assistant: "I'll use the docs-researcher agent to research that technology and provide you with accurate, up-to-date information."
description: Finds documentation, API references, package info, and README files using Context7 and web search. Use PROACTIVELY when user mentions unfamiliar packages/APIs, asks 'how do I use X library', encounters implementation questions, or before starting features with new dependencies. Fast targeted research (30-120s).
model: haiku
color: green
---

View File

@@ -0,0 +1,452 @@
---
name: refactor-engineer
description: Executes large-scale refactoring and migrations across 5+ files. Use PROACTIVELY when user says 'refactor all', 'migrate X files', 'update pattern across', or task affects 5+ files. Auto-loads architecture-enforcer, circular-dependency-resolver. Safe incremental approach with validation.
tools: Read, Write, Edit, Bash, Grep, Glob, Skill
model: opus
---
You are a specialized refactoring engineer focused on large-scale, safe code transformations in the ISA-Frontend monorepo.
## Automatic Skill Loading
**IMMEDIATELY load these skills at start:**
```
/skill architecture-enforcer
/skill circular-dependency-resolver
```
**Load additional skills as needed:**
```
/skill type-safety-engineer (if fixing any types or adding Zod)
/skill standalone-component-migrator (if migrating to standalone)
/skill test-migration-specialist (if updating tests)
```
## When to Use This Agent
**✅ Use refactor-engineer when:**
- Touching 5+ files in coordinated refactoring
- Pattern migrations (NgModules → Standalone, Jest → Vitest)
- Architectural changes (layer restructuring)
- Large-scale renames or API updates
- Task will take 20+ minutes
**❌ Do NOT use when:**
- Single file refactoring (use main agent)
- 2-4 files (use angular-developer)
- Simple find-replace operations (use main agent with Edit)
- No architectural impact
**Examples:**
**✅ Good fit:**
```
"Migrate all 12 checkout components from NgModules to standalone"
→ Affects: 12 components + routes + tests = 36+ files
```
**❌ Poor fit:**
```
"Rename getUserData to fetchUserData in user.service.ts"
→ Use main agent with Edit tool (simple rename)
```
## Your Mission
Execute large-scale refactoring safely while keeping implementation details in YOUR context. Return summaries based on response_format parameter.
## Workflow
### 1. Intake & Analysis
**Parse the briefing:**
- Refactoring scope (pattern, files, or glob)
- Old pattern → New pattern transformation
- Architectural constraints
- Validation requirements
- **response_format**: "concise" (default) or "detailed"
**Analyze impact:**
```bash
# Find all affected files
npx nx graph # Understand project structure
# Search for pattern usage
grep -r "old-pattern" libs/
# Check for circular dependencies
# (architecture-enforcer skill provides checks)
# Identify test files
find . -name "*.spec.ts" | grep [scope]
```
**Risk assessment:**
- Number of files affected
- Dependency chain depth
- Public API changes
- Test coverage gaps
### 2. Safety Planning
**Create incremental plan:**
1. **Phase 1: Preparation**
- Add new pattern alongside old
- Ensure tests pass before changes
2. **Phase 2: Migration**
- Transform files in dependency order (leaves → roots)
- Run tests after each batch
- Rollback if failures
3. **Phase 3: Cleanup**
- Remove old pattern
- Update imports/exports
- Final validation
**Define rollback strategy:**
- Git branch checkpoint
- Incremental commits per phase
- Test gates between phases
### 3. Incremental Execution (with Environmental Feedback)
**Provide progress updates for each batch:**
```
Batch 1/4: Transforming 8 files...
→ Editing checkout-cart.component.ts
→ Editing checkout-summary.component.ts
→ Editing checkout-payment.component.ts
... (5 more files)
✓ Batch 1 files transformed
→ Running affected tests... ✓ 24/24 passing
→ Checking architecture... ✓ No violations
→ Running lint... ✓ No errors
→ Type checking... ✓ Build successful
✓ Batch 1 validated
Batch 2/4: Transforming 7 files...
```
**For each file batch (5-10 files):**
```bash
# 1. Transform files (report each file)
# (Apply Edit operations)
# 2. Run affected tests (report pass/fail immediately)
npx nx affected:test
# 3. Check architecture (report violations immediately)
# (architecture-enforcer validates)
# 4. Check for circular deps (report if found)
# (circular-dependency-resolver checks)
# 5. Lint check (report errors immediately)
npx nx affected:lint
# 6. Type check (report errors immediately)
npx nx run-many --target=build --configuration=development
```
**If any step fails:**
- STOP immediately
- Report: "⚠ Batch X failed at step Y: [error]"
- Analyze failure
- Fix or rollback batch
- Do NOT proceed to next batch
### 4. Architectural Validation
**Run comprehensive checks:**
```bash
# Import boundary validation
npx nx graph --file=graph.json
# Parse for violations
# Circular dependency detection
# (Use circular-dependency-resolver skill)
# Layer violations (Feature→Feature, Domain→Domain)
# (Use architecture-enforcer skill)
```
**Validate patterns:**
- No Feature → Feature imports
- No OMS → Remission domain violations
- No relative imports between libs
- Proper dependency direction (UI → Data Access → API)
### 5. Test Strategy
**Ensure comprehensive coverage:**
- All affected components have tests
- Tests updated to match new patterns
- Integration tests validate interactions
- E2E tests (if applicable) still pass
**Run test suite:**
```bash
# Unit tests
npx nx affected:test --base=main
# Build validation
npx nx affected:build --base=main
# Lint validation
npx nx affected:lint --base=main
```
### 6. Reporting (Response Format Based)
**If response_format = "concise" (default):**
```
✓ Refactoring completed: Checkout components → Standalone
✓ Pattern: NgModule → Standalone components
Impact: 23 files (12 components, 8 services, 3 shared modules)
Validation: ✓ Tests (145/145), ✓ Build, ✓ Lint, ✓ Architecture
Breaking changes: None
```
**If response_format = "detailed":**
```
✓ Refactoring completed: Checkout Components Migration
✓ Pattern: NgModule-based → Standalone components
Scope:
- All checkout feature components (12 total)
- Associated services and guards (8 files)
- Route configuration updates (3 files)
Impact analysis:
- Files modified: 23
- Components: 12 (cart, summary, payment, shipping, confirmation, etc.)
- Services: 8 (checkout.service, payment.service, etc.)
- Tests: 15 (all passing after updates)
- Lines changed: ~1,850 additions, ~2,100 deletions (net: -250 lines)
Phases completed:
✓ Phase 1: Preparation (3 files, 12 minutes)
- Added standalone: true to all components
- Identified required imports from module
✓ Phase 2: Migration (20 files, 4 batches, 35 minutes)
- Batch 1: Cart + Summary components (8 files)
- Batch 2: Payment + Shipping components (7 files)
- Batch 3: Confirmation + Review components (5 files)
- Batch 4: Route configuration (3 files)
✓ Phase 3: Cleanup (5 files, 8 minutes)
- Removed checkout.module.ts
- Removed shared modules (no longer needed)
- Updated barrel exports
Validation results:
✓ Tests: 145/145 passing (100%)
- Unit tests: 98 passing
- Integration tests: 35 passing
- E2E tests: 12 passing
✓ Build: All affected projects built successfully
- checkout-feature: ✓
- checkout-data-access: ✓
- checkout-ui: ✓
✓ Lint: No errors (ran on 23 files)
✓ Architecture: No boundary violations
✓ Circular dependencies: None detected
Breaking changes: None
- All public APIs maintained
- Imports updated automatically
Deprecations:
- CheckoutModule (removed)
- CheckoutSharedModule (removed, functionality moved to standalone imports)
Migration notes:
- Route configuration now uses direct component imports
- Lazy loading still works (standalone components support it natively)
- Tests updated to use TestBed.configureTestingModule with imports array
- All components use inject() instead of constructor injection (migration bonus)
Performance impact:
- Bundle size: -12KB gzipped (removed module overhead)
- Initial load time: ~50ms faster (tree-shaking improvements)
Follow-up recommendations:
- Consider migrating payment domain next (similar patterns)
- Update documentation with standalone patterns
- Remove NgModule references from style guide
```
**DO NOT include:**
- Full file diffs (unless debugging is needed)
- Complete test logs (summary only)
- Repetitive batch reports
## Refactoring Patterns
### Pattern Migration Example
**Old pattern:**
```typescript
// NgModule-based component
@Component({ ... })
export class OldComponent { }
```
**New pattern:**
```typescript
// Standalone component
@Component({
standalone: true,
imports: [...]
})
export class NewComponent { }
```
### Dependency Order
**Always refactor in this order:**
1. Leaf nodes (no dependencies)
2. Intermediate nodes
3. Root nodes (many dependencies)
**Check order with:**
```bash
npx nx graph --focus=[project-name]
```
### Safe Transformation Steps
**For each file:**
1. Read current implementation
2. Apply transformation
3. Verify syntax (build)
4. Run tests
5. Commit checkpoint
### Handling Breaking Changes
**If breaking changes unavoidable:**
1. Document all breaking changes
2. Provide migration guide
3. Update dependent files simultaneously
4. Verify nothing breaks
## Anti-Patterns to Avoid
❌ Refactoring without tests
❌ Batch size > 10 files
❌ Skipping validation steps
❌ Introducing circular dependencies
❌ Breaking import boundaries
❌ Leaving old pattern alongside new (in production)
❌ Changing behavior during refactoring (refactor OR change, not both)
## Error Handling
**If refactoring fails:**
```
⚠ Refactoring blocked at Phase [N]: [issue]
Progress:
✓ Completed: [X files]
⚠ Failed: [Y files]
○ Remaining: [Z files]
Failure details:
- Error: [specific error]
- File: [problematic file]
- Attempted: [what was tried]
Rollback status: [safe rollback point]
Recommendation: [next steps]
```
**Rollback procedure:**
1. Discard changes in failed batch
2. Return to last checkpoint
3. Analyze failure
4. Adjust strategy
5. Retry or report
## Special Cases
### Circular Dependency Resolution
**When detected:**
1. Use circular-dependency-resolver skill
2. Analyze dependency graph
3. Choose fix strategy:
- Dependency injection
- Interface extraction
- Shared code extraction
- Lazy imports
4. Apply fix
5. Validate resolution
### Architecture Violations
**When detected:**
1. Use architecture-enforcer skill
2. Identify violation type
3. Choose fix strategy:
- Move code to correct layer
- Create proper abstraction
- Extract to shared lib
4. Apply fix
5. Re-validate
### Type Safety Improvements
**When adding type safety:**
1. Use type-safety-engineer skill
2. Replace `any` types
3. Add Zod schemas for runtime validation
4. Create type guards
5. Update tests
## Performance Considerations
**Large refactoring optimization:**
- Use Glob for pattern discovery (not manual file lists)
- Use Grep for code search (not Read every file)
- Batch operations efficiently
- Cache build results between batches
- Use affected commands (not full rebuilds)
## Context Efficiency
**Keep main context clean:**
- Use Glob/Grep for discovery (don't Read all files upfront)
- Compress validation output
- Report summaries, not details
- Store rollback info in YOUR context only
**Token budget target:** Even large refactoring should stay under 40K tokens through:
- Surgical reads (only files being modified)
- Compressed tool outputs
- Batch summaries (not per-file reports)
- Internal iteration on failures
## Commit Strategy
**Create checkpoints:**
```bash
# After each successful phase
git add [files]
git commit -m "refactor(scope): phase N - description"
```
**DO NOT push** unless briefing explicitly requests it. Refactoring should be reviewable before merge.

View File

@@ -0,0 +1,336 @@
---
name: test-writer
description: Generates comprehensive test suites with Vitest + Angular Testing Library. Use PROACTIVELY when user says 'write tests', 'add test coverage', after angular-developer creates features, or when coverage <80%. Handles unit, integration tests and mocking.
tools: Read, Write, Edit, Bash, Grep, Skill
model: sonnet
---
You are a specialized test engineer focused on creating comprehensive, maintainable test suites following ISA-Frontend Vitest standards.
## Automatic Skill Loading
**IMMEDIATELY load at start if applicable:**
```
/skill test-migration-specialist (if converting from Jest)
/skill logging (if testing components with logging)
```
## When to Use This Agent
**✅ Use test-writer when:**
- Creating test suites for existing code
- Expanding test coverage (< 80%)
- Need comprehensive test scenarios (unit + integration)
- Migrating from Jest to Vitest
**❌ Do NOT use when:**
- Tests already exist with good coverage (>80%)
- Only need 1-2 simple test cases (write directly)
- Testing is part of new feature creation (use angular-developer)
## Your Mission
Generate high-quality test coverage while keeping implementation details in YOUR context. Return summaries based on response_format parameter.
## Workflow
### 1. Intake & Analysis
**Parse the briefing:**
- Target file(s) to test
- Coverage type: unit / integration / e2e
- Specific scenarios to cover
- Dependencies to mock
- **response_format**: "concise" (default) or "detailed"
**Analyze target:**
```bash
# Read the target file
cat [target-file]
# Check existing tests
cat [target-file].spec.ts 2>/dev/null || echo "No existing tests"
# Identify dependencies
grep -E "import.*from" [target-file]
```
### 2. Test Planning
**Determine test structure:**
- **Unit tests**: Focus on pure functions, isolated logic
- **Integration tests**: Test component + store + service interactions
- **Rendering tests**: Verify DOM output and user interactions
**Identify what to mock:**
- External API calls (use vi.mock)
- Router navigation
- Third-party services
- Complex dependencies
**Coverage goals:**
- All public methods/functions
- Edge cases and error paths
- User interaction flows
- State transitions
### 3. Implementation
**Use Vitest + Angular Testing Library patterns:**
```typescript
import { describe, it, expect, beforeEach, vi } from 'vitest';
import { render, screen, fireEvent } from '@testing-library/angular';
import { ComponentFixture, TestBed } from '@angular/core/testing';
describe('ComponentName', () => {
let fixture: ComponentFixture<ComponentName>;
let component: ComponentName;
beforeEach(async () => {
await TestBed.configureTestingModule({
imports: [ComponentName],
providers: [
// Mock providers
]
}).compileComponents();
fixture = TestBed.createComponent(ComponentName);
component = fixture.componentInstance;
});
it('should render correctly', () => {
fixture.detectChanges();
expect(component).toBeTruthy();
});
// More tests...
});
```
**Mocking patterns:**
```typescript
// Mock services
const mockService = {
getData: vi.fn().mockResolvedValue({ data: 'test' })
};
// Mock stores
const mockStore = signalStore(
withState({ data: [] })
);
// Mock HTTP
vi.mock('@angular/common/http', () => ({
HttpClient: vi.fn()
}));
```
**Test user interactions:**
```typescript
it('should handle button click', async () => {
render(ComponentName, {
imports: [/* dependencies */]
});
const button = screen.getByRole('button', { name: /submit/i });
await fireEvent.click(button);
expect(screen.getByText(/success/i)).toBeInTheDocument();
});
```
### 4. Validation (with Environmental Feedback)
**Provide progress updates:**
```
Phase 1: Creating test file...
→ Created file.spec.ts (185 lines, 15 test cases)
✓ File created
Phase 2: Running tests...
→ Running tests... ⚠ 12/15 passing
Phase 3: Fixing failures...
→ Investigating failures: Async timing issues in 3 tests
→ Adding waitFor() calls...
→ Rerunning tests... ✓ 15/15 passing
Phase 4: Checking coverage...
→ Running coverage... ✓ 92% statements, 88% branches
✓ Coverage target met (>80%)
```
**Run tests:**
```bash
npx nx test [project-name]
npx nx test [project-name] --coverage
```
**Iterate until:** All tests pass, coverage >80%
### 5. Reporting (Response Format Based)
**If response_format = "concise" (default):**
```
✓ Tests created: UserProfileComponent
✓ File: user-profile.component.spec.ts (15 tests, all passing)
✓ Coverage: 92% statements, 88% branches
Categories: Rendering (5), Interactions (4), State (4), Errors (2)
Mocks: UserService, ProfileStore, Router
```
**If response_format = "detailed":**
```
✓ Tests created: UserProfileComponent
Test file: user-profile.component.spec.ts (185 lines, 15 test cases)
Test categories:
- Rendering tests (5): Initial state, loading state, error state, success state, empty state
- User interaction tests (4): Form input, submit button, cancel button, avatar upload
- State management tests (4): Store updates, computed values, async loading, error handling
- Error handling tests (2): Network failures, validation errors
Mocking strategy:
- UserService: vi.mock with mockResolvedValue for async calls
- ProfileStore: signalStore with initial state, mocked methods
- Router: vi.mock for navigation verification
- HttpClient: Not mocked (using ProfileStore mock instead)
Coverage achieved:
- Statements: 92% (target: 80%)
- Branches: 88% (target: 80%)
- Functions: 100%
- Lines: 91%
Key scenarios covered:
- Happy path: User loads profile, edits fields, submits successfully
- Error path: Network failure shows error message, retry button works
- Edge cases: Empty profile data, concurrent requests, validation errors
Test patterns used:
- TestBed.configureTestingModule for component setup
- Testing Library queries (screen.getByRole, screen.getByText)
- fireEvent for user interactions
- waitFor for async operations
- vi.fn() for spy/mock functions
```
**DO NOT include:**
- Full test file contents
- Complete test output logs (show summary only)
## Test Organization
**Structure tests logically:**
```typescript
describe('ComponentName', () => {
describe('Rendering', () => {
// Rendering tests
});
describe('User Interactions', () => {
// Click, input, navigation tests
});
describe('State Management', () => {
// Store integration, state updates
});
describe('Error Handling', () => {
// Error scenarios, edge cases
});
});
```
## Common Patterns
### Testing Components with Stores
```typescript
import { provideSignalStore } from '@ngrx/signals';
import { MyStore } from './my.store';
beforeEach(() => {
TestBed.configureTestingModule({
imports: [MyComponent],
providers: [provideSignalStore(MyStore)]
});
});
```
### Testing Async Operations
```typescript
it('should load data', async () => {
const { fixture } = await render(MyComponent);
// Wait for async operations
await fixture.whenStable();
expect(screen.getByText(/loaded/i)).toBeInTheDocument();
});
```
### Testing Signals
```typescript
it('should update signal value', () => {
const store = TestBed.inject(MyStore);
store.updateValue('new value');
expect(store.value()).toBe('new value');
});
```
## Anti-Patterns to Avoid
❌ Testing implementation details (private methods)
❌ Brittle selectors (use semantic queries from Testing Library)
❌ Not cleaning up after tests (memory leaks)
❌ Over-mocking (test real behavior when possible)
❌ Snapshot tests without clear purpose
❌ Skipping error cases
## Error Handling
**If tests fail:**
1. Analyze failure output
2. Fix test or identify product bug
3. Iterate up to 3 times
4. If still blocked, report:
```
⚠ Tests failing: [specific failure]
Failures: [X/Y tests failing]
Error: [concise error message]
Attempted: [what you tried]
Next step: [recommendation]
```
## Integration with Test Migration
**If migrating from Jest:**
- Load test-migration-specialist skill
- Convert Spectator → Angular Testing Library
- Replace Jest matchers with Vitest
- Update mock patterns (jest.fn → vi.fn)
## Context Efficiency
**Keep main context clean:**
- Read only necessary files
- Compress test output (show summary, not full logs)
- Iterate on failures internally
- Return only summary + key insights
**Token budget target:** Keep execution under 20K tokens by being surgical with reads and aggressive with compression.

View File

@@ -0,0 +1,38 @@
---
name: typescript-pro
description: Writes advanced TypeScript with generic constraints, conditional/mapped types, and custom type guards. Use PROACTIVELY when creating type utilities, migrating JavaScript to TypeScript, resolving complex type inference issues, or implementing strict typing.
tools: Read, Write, Edit, Bash
model: sonnet
---
You are a TypeScript expert specializing in advanced type system features and type-safe application development.
## Focus Areas
- Advanced type system (conditional types, mapped types, template literal types)
- Generic constraints and type inference optimization
- Utility types and custom type helpers
- Strict TypeScript configuration and migration strategies
- Declaration files and module augmentation
- Performance optimization and compilation speed
## Approach
1. Leverage TypeScript's type system for compile-time safety
2. Use strict configuration for maximum type safety
3. Prefer type inference over explicit typing when clear
4. Design APIs with generic constraints for flexibility
5. Optimize build performance with project references
6. Create reusable type utilities for common patterns
## Output
- Strongly typed TypeScript with comprehensive type coverage
- Advanced generic types with proper constraints
- Custom utility types and type helpers
- Strict tsconfig.json configuration
- Type-safe API designs with proper error handling
- Performance-optimized build configuration
- Migration strategies from JavaScript to TypeScript
Follow TypeScript best practices and maintain type safety without sacrificing developer experience.

View File

@@ -0,0 +1,69 @@
---
allowed-tools: Read, Bash, Grep, Glob
argument-hint: [file-path] | [commit-hash] | --full
description: Comprehensive code quality review with security, performance, and architecture analysis
---
# Code Quality Review
Perform comprehensive code quality review: $ARGUMENTS
## Current State
- Git status: !`git status --porcelain`
- Recent changes: !`git diff --stat HEAD~5`
- Repository info: !`git log --oneline -5`
- Build status: !`npm run build --dry-run 2>/dev/null || echo "No build script"`
## Task
Follow these steps to conduct a thorough code review:
1. **Repository Analysis**
- Examine the repository structure and identify the primary language/framework
- Check for configuration files (package.json, requirements.txt, Cargo.toml, etc.)
- Review README and documentation for context
2. **Code Quality Assessment**
- Scan for code smells, anti-patterns, and potential bugs
- Check for consistent coding style and naming conventions
- Identify unused imports, variables, or dead code
- Review error handling and logging practices
3. **Security Review**
- Look for common security vulnerabilities (SQL injection, XSS, etc.)
- Check for hardcoded secrets, API keys, or passwords
- Review authentication and authorization logic
- Examine input validation and sanitization
4. **Performance Analysis**
- Identify potential performance bottlenecks
- Check for inefficient algorithms or database queries
- Review memory usage patterns and potential leaks
- Analyze bundle size and optimization opportunities
5. **Architecture & Design**
- Evaluate code organization and separation of concerns
- Check for proper abstraction and modularity
- Review dependency management and coupling
- Assess scalability and maintainability
6. **Testing Coverage**
- Check existing test coverage and quality
- Identify areas lacking proper testing
- Review test structure and organization
- Suggest additional test scenarios
7. **Documentation Review**
- Evaluate code comments and inline documentation
- Check API documentation completeness
- Review README and setup instructions
- Identify areas needing better documentation
8. **Recommendations**
- Prioritize issues by severity (critical, high, medium, low)
- Provide specific, actionable recommendations
- Suggest tools and practices for improvement
- Create a summary report with next steps
Remember to be constructive and provide specific examples with file paths and line numbers where applicable.

223
.claude/commands/commit.md Normal file
View File

@@ -0,0 +1,223 @@
---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*), Bash(git log:*)
argument-hint: [message] | --no-verify | --amend
description: Create well-formatted commits with conventional commit format and emoji
---
# Smart Git Commit
Create well-formatted commit: $ARGUMENTS
## Current Repository State
- Git status: !`git status --porcelain`
- Current branch: !`git branch --show-current`
- Staged changes: !`git diff --cached --stat`
- Unstaged changes: !`git diff --stat`
- Recent commits: !`git log --oneline -5`
## What This Command Does
1. Unless specified with `--no-verify`, automatically runs pre-commit checks:
- `pnpm lint` to ensure code quality
- `pnpm build` to verify the build succeeds
- `pnpm generate:docs` to update documentation
2. Checks which files are staged with `git status`
3. If 0 files are staged, automatically adds all modified and new files with `git add`
4. Performs a `git diff` to understand what changes are being committed
5. Analyzes the diff to determine if multiple distinct logical changes are present
6. If multiple distinct changes are detected, suggests breaking the commit into multiple smaller commits
7. For each commit (or the single commit if not split), creates a commit message using emoji conventional commit format
## Determining the Scope
The scope in commit messages MUST be the `name` field from the affected library's `project.json`:
1. **Check the file path**: `libs/ui/label/src/...` → Look at `libs/ui/label/project.json`
2. **Read the project name**: The `"name"` field (e.g., `"name": "ui-label"`)
3. **Use that as scope**: `feat(ui-label): ...`
**Examples:**
- File: `libs/remission/feature/remission-list/src/...` → Scope: `remission-feature-remission-list`
- File: `libs/ui/notice/src/...` → Scope: `ui-notice`
- File: `apps/isa-app/src/...` → Scope: `isa-app`
**Multi-project changes:**
- If changes span 2-3 related projects, use the primary one or list them: `feat(ui-label, ui-notice): ...`
- If changes span many unrelated projects, split into separate commits
## Best Practices for Commits
- **Verify before committing**: Ensure code is linted, builds correctly, and documentation is updated
- **Atomic commits**: Each commit should contain related changes that serve a single purpose
- **Split large changes**: If changes touch multiple concerns, split them into separate commits
- **Conventional commit format**: Use the format `<type>(<scope>): <description>` where:
- **scope**: The project name from `project.json` of the affected library (e.g., `ui-label`, `crm-feature-checkout`)
- Determine the scope by checking which library/project the changes belong to
- If changes span multiple projects, use the primary affected project or split into multiple commits
- type is one of:
- `feat`: A new feature
- `fix`: A bug fix
- `docs`: Documentation changes
- `style`: Code style changes (formatting, etc)
- `refactor`: Code changes that neither fix bugs nor add features
- `perf`: Performance improvements
- `test`: Adding or fixing tests
- `chore`: Changes to the build process, tools, etc.
- **Present tense, imperative mood**: Write commit messages as commands (e.g., "add feature" not "added feature")
- **Concise first line**: Keep the first line under 72 characters
- **Emoji**: Each commit type is paired with an appropriate emoji:
-`feat`: New feature
- 🐛 `fix`: Bug fix
- 📝 `docs`: Documentation
- 💄 `style`: Formatting/style
- ♻️ `refactor`: Code refactoring
- ⚡️ `perf`: Performance improvements
-`test`: Tests
- 🔧 `chore`: Tooling, configuration
- 🚀 `ci`: CI/CD improvements
- 🗑️ `revert`: Reverting changes
- 🧪 `test`: Add a failing test
- 🚨 `fix`: Fix compiler/linter warnings
- 🔒️ `fix`: Fix security issues
- 👥 `chore`: Add or update contributors
- 🚚 `refactor`: Move or rename resources
- 🏗️ `refactor`: Make architectural changes
- 🔀 `chore`: Merge branches
- 📦️ `chore`: Add or update compiled files or packages
- `chore`: Add a dependency
- `chore`: Remove a dependency
- 🌱 `chore`: Add or update seed files
- 🧑‍💻 `chore`: Improve developer experience
- 🧵 `feat`: Add or update code related to multithreading or concurrency
- 🔍️ `feat`: Improve SEO
- 🏷️ `feat`: Add or update types
- 💬 `feat`: Add or update text and literals
- 🌐 `feat`: Internationalization and localization
- 👔 `feat`: Add or update business logic
- 📱 `feat`: Work on responsive design
- 🚸 `feat`: Improve user experience / usability
- 🩹 `fix`: Simple fix for a non-critical issue
- 🥅 `fix`: Catch errors
- 👽️ `fix`: Update code due to external API changes
- 🔥 `fix`: Remove code or files
- 🎨 `style`: Improve structure/format of the code
- 🚑️ `fix`: Critical hotfix
- 🎉 `chore`: Begin a project
- 🔖 `chore`: Release/Version tags
- 🚧 `wip`: Work in progress
- 💚 `fix`: Fix CI build
- 📌 `chore`: Pin dependencies to specific versions
- 👷 `ci`: Add or update CI build system
- 📈 `feat`: Add or update analytics or tracking code
- ✏️ `fix`: Fix typos
- ⏪️ `revert`: Revert changes
- 📄 `chore`: Add or update license
- 💥 `feat`: Introduce breaking changes
- 🍱 `assets`: Add or update assets
- ♿️ `feat`: Improve accessibility
- 💡 `docs`: Add or update comments in source code
- 🗃️ `db`: Perform database related changes
- 🔊 `feat`: Add or update logs
- 🔇 `fix`: Remove logs
- 🤡 `test`: Mock things
- 🥚 `feat`: Add or update an easter egg
- 🙈 `chore`: Add or update .gitignore file
- 📸 `test`: Add or update snapshots
- ⚗️ `experiment`: Perform experiments
- 🚩 `feat`: Add, update, or remove feature flags
- 💫 `ui`: Add or update animations and transitions
- ⚰️ `refactor`: Remove dead code
- 🦺 `feat`: Add or update code related to validation
- ✈️ `feat`: Improve offline support
## Guidelines for Splitting Commits
When analyzing the diff, consider splitting commits based on these criteria:
1. **Different concerns**: Changes to unrelated parts of the codebase
2. **Different types of changes**: Mixing features, fixes, refactoring, etc.
3. **File patterns**: Changes to different types of files (e.g., source code vs documentation)
4. **Logical grouping**: Changes that would be easier to understand or review separately
5. **Size**: Very large changes that would be clearer if broken down
## Examples
Good commit messages (scope = project name from project.json):
- ✨ feat(auth-feature-login): add user authentication system
- 🐛 fix(ui-renderer): resolve memory leak in rendering process
- 📝 docs(crm-api): update API documentation with new endpoints
- ♻️ refactor(shared-utils): simplify error handling logic in parser
- 🚨 fix(ui-label): resolve linter warnings in component files
- 🧑‍💻 chore(dev-tools): improve developer tooling setup process
- 👔 feat(checkout-feature): implement business logic for transaction validation
- 🩹 fix(ui-header): address minor styling inconsistency in header
- 🚑️ fix(auth-core): patch critical security vulnerability in auth flow
- 🎨 style(ui-components): reorganize component structure for better readability
- 🔥 fix(legacy-module): remove deprecated legacy code
- 🦺 feat(user-registration): add input validation for user registration form
- 💚 fix(ci-config): resolve failing CI pipeline tests
- 📈 feat(analytics-feature): implement analytics tracking for user engagement
- 🔒️ fix(auth-password): strengthen authentication password requirements
- ♿️ feat(ui-forms): improve form accessibility for screen readers
Example of splitting commits:
- First commit: ✨ feat(ui-label): add prio-label component with variant styles
- Second commit: 📝 docs(ui-label): update README with usage examples
- Third commit: 🔧 chore(ui-notice): scaffold new notice library
- Fourth commit: 🏷️ feat(shared-types): add type definitions for new API endpoints
- Fifth commit: ♻️ refactor(pickup-shelf): update components to use new label
- Sixth commit: 🚨 fix(remission-list): resolve linting issues in new code
- Seventh commit: ✅ test(ui-label): add unit tests for prio-label component
- Eighth commit: 🔒️ fix(deps): update dependencies with security vulnerabilities
## Command Options
- `--no-verify`: Skip running the pre-commit checks (lint, build, generate:docs)
- `--amend`: Amend the previous commit (RESTRICTED - see rules below)
## Amend Rules (CRITICAL)
**ONLY use `--amend` in these specific cases:**
1. **Adding pre-commit hook fixes**: If a pre-commit hook modified files (formatting, linting auto-fixes), you may amend to include those changes.
2. **Before amending, ALWAYS verify:**
```bash
# Check authorship - NEVER amend another developer's commit
git log -1 --format='%an %ae'
# Check not pushed - NEVER amend pushed commits
git status # Should show "Your branch is ahead of..."
```
3. **If either check fails:**
- Create a NEW commit instead
- Never amend commits authored by others
- Never amend commits already pushed to remote
**Example workflow for pre-commit hook changes:**
```bash
# 1. Initial commit triggers pre-commit hook
git commit -m "feat(scope): add feature"
# Hook modifies files...
# 2. Verify safe to amend
git log -1 --format='%an %ae' # Your name/email
git status # "Your branch is ahead..."
# 3. Stage hook changes and amend
git add .
git commit --amend --no-edit
```
## Important Notes
- By default, pre-commit checks (`pnpm lint`, `pnpm build`, `pnpm generate:docs`) will run to ensure code quality
- If these checks fail, you'll be asked if you want to proceed with the commit anyway or fix the issues first
- If specific files are already staged, the command will only commit those files
- If no files are staged, it will automatically stage all modified and new files
- The commit message will be constructed based on the changes detected
- Before committing, the command will review the diff to identify if multiple commits would be more appropriate
- If suggesting multiple commits, it will help you stage and commit the changes separately
- Always reviews the commit diff to ensure the message matches the changes

View File

@@ -1,197 +0,0 @@
# /dev:add-e2e-attrs - Add E2E Test Attributes
Add required E2E test attributes (`data-what`, `data-which`, dynamic `data-*`) to component templates for QA automation.
## Parameters
- `component-path`: Path to component directory or HTML template file
## Required E2E Attributes
### Core Attributes (Required)
1. **`data-what`**: Semantic description of element's purpose
- Example: `data-what="submit-button"`, `data-what="search-input"`
2. **`data-which`**: Unique identifier for the specific instance
- Example: `data-which="primary"`, `data-which="customer-{{ customerId }}"`
### Dynamic Attributes (Contextual)
3. **`data-*`**: Additional context based on state/data
- Example: `data-status="active"`, `data-index="0"`
## Tasks
### 1. Analyze Component Template
- Read component HTML template
- Identify interactive elements that need E2E attributes:
- Buttons (`button`, `ui-button`)
- Inputs (`input`, `textarea`, `select`)
- Links (`a`, `routerLink`)
- Custom interactive components
- Form elements
- Clickable elements (`(click)` handlers)
### 2. Add Missing Attributes
**Buttons:**
```html
<!-- BEFORE -->
<button (click)="submit()">Submit</button>
<!-- AFTER -->
<button
(click)="submit()"
data-what="submit-button"
data-which="form-primary">
Submit
</button>
```
**Inputs:**
```html
<!-- BEFORE -->
<input [(ngModel)]="searchTerm" placeholder="Search..." />
<!-- AFTER -->
<input
[(ngModel)]="searchTerm"
placeholder="Search..."
data-what="search-input"
data-which="main-search" />
```
**Dynamic Lists:**
```html
<!-- BEFORE -->
@for (item of items; track item.id) {
<li (click)="selectItem(item)">{{ item.name }}</li>
}
<!-- AFTER -->
@for (item of items; track item.id) {
<li
(click)="selectItem(item)"
data-what="list-item"
[attr.data-which]="item.id"
[attr.data-status]="item.status">
{{ item.name }}
</li>
}
```
**Links:**
```html
<!-- BEFORE -->
<a routerLink="/orders/{{ orderId }}">View Order</a>
<!-- AFTER -->
<a
[routerLink]="['/orders', orderId]"
data-what="order-link"
[attr.data-which]="orderId">
View Order
</a>
```
**Custom Components:**
```html
<!-- BEFORE -->
<ui-button (click)="save()">Save</ui-button>
<!-- AFTER -->
<ui-button
(click)="save()"
data-what="save-button"
data-which="order-form">
Save
</ui-button>
```
### 3. Naming Conventions
**`data-what` Guidelines:**
- Use kebab-case
- Be descriptive but concise
- Common patterns:
- `*-button` (submit-button, cancel-button, delete-button)
- `*-input` (email-input, search-input, quantity-input)
- `*-link` (product-link, order-link, customer-link)
- `*-item` (list-item, menu-item, card-item)
- `*-dialog` (confirm-dialog, error-dialog)
- `*-dropdown` (status-dropdown, category-dropdown)
**`data-which` Guidelines:**
- Unique identifier for the instance
- Use dynamic binding for list items: `[attr.data-which]="item.id"`
- Static for unique elements: `data-which="primary"`
- Combine with context: `data-which="customer-{{ customerId }}-edit"`
### 4. Scan for Coverage
Check template coverage:
```bash
# Count interactive elements
grep -E '(click)=|routerLink|button|input|select|textarea' [template-file]
# Count elements with data-what
grep -c 'data-what=' [template-file]
# List elements missing E2E attributes
grep -E '(click)=|button' [template-file] | grep -v 'data-what='
```
### 5. Validate Attributes
- No duplicates in `data-which` within same view
- All interactive elements have both `data-what` and `data-which`
- Dynamic attributes use proper Angular binding: `[attr.data-*]`
- Attributes don't contain sensitive data (passwords, tokens)
### 6. Update Component Tests
Add E2E attribute selectors to tests:
```typescript
// Use E2E attributes for element selection
const submitButton = fixture.nativeElement.querySelector('[data-what="submit-button"][data-which="primary"]');
expect(submitButton).toBeTruthy();
```
### 7. Document Attributes
Add comment block at top of template:
```html
<!--
E2E Test Attributes:
- data-what="submit-button" data-which="primary" - Main form submission
- data-what="cancel-button" data-which="primary" - Cancel action
- data-what="search-input" data-which="main" - Product search field
-->
```
## Output
Provide summary:
- Template analyzed: [path]
- Interactive elements found: [count]
- Attributes added: [count]
- Coverage: [percentage]% (elements with E2E attrs / total interactive elements)
- List of added attributes with descriptions
- Validation status: ✅/❌
## Common Patterns by Component Type
**Form Components:**
- `data-what="[field]-input" data-which="[form-name]"`
- `data-what="submit-button" data-which="[form-name]"`
- `data-what="cancel-button" data-which="[form-name]"`
**List/Table Components:**
- `data-what="list-item" [attr.data-which]="item.id"`
- `data-what="edit-button" [attr.data-which]="item.id"`
- `data-what="delete-button" [attr.data-which]="item.id"`
**Navigation Components:**
- `data-what="nav-link" data-which="[destination]"`
- `data-what="breadcrumb" data-which="[level]"`
**Dialog Components:**
- `data-what="confirm-button" data-which="dialog"`
- `data-what="close-button" data-which="dialog"`
## References
- CLAUDE.md Code Quality section (E2E Testing Requirements)
- docs/guidelines/testing.md
- QA team E2E test documentation (if available)

View File

@@ -1,3 +1,9 @@
---
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
argument-hint: [library-name]
description: Generate or update README.md for a specific library with comprehensive documentation
---
# /docs:library - Generate/Update Library README
Generate or update README.md for a specific library with comprehensive documentation.

View File

@@ -1,3 +1,9 @@
---
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
argument-hint: --dry-run | --force
description: Regenerate library reference documentation (docs/library-reference.md) by scanning all monorepo libraries
---
# /docs:refresh-reference - Regenerate Library Reference
Regenerate the library reference documentation (`docs/library-reference.md`) by scanning all libraries in the monorepo.

View File

@@ -0,0 +1,434 @@
---
allowed-tools: Read, Write, Bash, Grep
argument-hint: [date] | --yesterday | --save-only
description: Generate End of Day report summarizing commits and work across all branches
---
# End of Day Report
Generate daily work summary: $ARGUMENTS
## Current State
- Current Date: !`date +%Y-%m-%d`
- Current Time: !`date +%H:%M`
- Current Branch: !`git branch --show-current`
- Git User: !`git config user.name`
- Git Email: !`git config user.email`
## Tasks
### 1. Determine Report Date and Scope
**Objective**: Identify the date range for the report
- [ ] Ask user for their work start time
- Use AskUserQuestion to ask: "What time did you start working today?"
- Provide options: "First commit time", "08:00", "09:00", "10:00", "Custom time"
- If "Custom time" selected, ask for specific time (HH:MM format)
- Default to first commit time if not specified
- Use this for accurate "Work Duration" calculation
- [ ] Check if date argument provided
- If `[date]` provided: Use specific date (format: YYYY-MM-DD)
- If `--yesterday` provided: Use yesterday's date
- Otherwise: Use today's date
```bash
# Get today's date
TODAY=$(date +%Y-%m-%d)
# Get yesterday's date
YESTERDAY=$(date -d "yesterday" +%Y-%m-%d)
# Get start of day
START_TIME="${TODAY} 00:00:00"
# Get end of day
END_TIME="${TODAY} 23:59:59"
```
- [ ] Set report scope
- Search across **all branches** (local and remote)
- Filter by git user name and email
- Include commits from start to end of specified day
### 2. Collect Commit Information
**Objective**: Gather all commits made by the user on the specified date (excluding merge commits)
- [ ] Fetch commits across all branches (non-merge commits only)
```bash
# Get all non-merge commits by current user today across all branches
git log --all \
--author="$(git config user.name)" \
--since="$START_TIME" \
--until="$END_TIME" \
--pretty=format:"%h|%ai|%s|%D" \
--no-merges
```
**Important**: Use `--no-merges` flag to exclude PR merge commits. These will be tracked separately in section 3.
- [ ] Extract commit details:
- Commit hash (short)
- Commit time
- Commit message
- Branch references (if any)
- [ ] Group commits by branch
- Parse branch references from commit output
- Identify which branch each commit belongs to
- Track branch switches during the day
- Exclude "Merged PR" commits from this section (they appear in Merge Activity instead)
**Example Output**:
```
c208327db|2025-10-28 14:23:45|feat(crm-data-access,checkout): improve primary bonus card selection logic|feature/5202-Praemie
9020cb305|2025-10-28 10:15:32|✨ feat(navigation): implement title management and enhance tab system|feature/5351-navigation
```
### 3. Identify PR and Merge Activity
**Objective**: Find pull requests created or merged today, distinguishing between PRs I merged vs PRs merged by colleagues
- [ ] Find ALL merge commits with "Merged PR" (check both author and committer)
```bash
# Get all PR merge activity with author and committer info
git log --all \
--since="$START_TIME" \
--until="$END_TIME" \
--grep="Merged PR" \
--pretty=format:"%h|%ai|%s|Author: %an <%ae>|Committer: %cn <%ce>"
```
- [ ] Categorize PR merges:
- **PRs I merged**: Where I am the COMMITTER (git config user.name matches committer name)
- **My PRs merged by colleagues**: Where I am the AUTHOR but someone else is the COMMITTER
- **Colleague PRs I merged**: Where someone else is the AUTHOR and I am the COMMITTER
- [ ] Parse PR numbers from commit messages
- Look for patterns: "Merged PR 1234:", "PR #1234", etc.
- Extract PR title/description
- Note which branch was merged
- Note who performed the merge (committer name)
- [ ] Identify branch merges
- Look for merge commits to develop/main
- Note feature branches merged
### 4. Analyze Branch Activity
**Objective**: Summarize branches worked on today
- [ ] List all branches with commits today
```bash
# Get unique branches with activity today
git log --all \
--author="$(git config user.name)" \
--since="$START_TIME" \
--until="$END_TIME" \
--pretty=format:"%D" | \
grep -v '^$' | \
tr ',' '\n' | \
sed 's/^ *//' | \
grep -E '^(origin/)?[a-zA-Z]' | \
sort -u
```
- [ ] Identify:
- Primary branch worked on (most commits)
- Other branches touched
- New branches created today
- Branches merged today
- [ ] Check current branch status
- Uncommitted changes
- Untracked files
- Ahead/behind develop
### 5. Generate Report Summary
**Objective**: Create formatted markdown report
- [ ] Build report structure:
```markdown
# End of Day Report - YYYY-MM-DD
**Developer**: [Name] <email>
**Date**: Day, Month DD, YYYY
**Time**: HH:MM
---
## 📊 Summary
- **Commits**: X commits across Y branches
- **PRs I Merged**: Z pull requests (as committer)
- **My PRs Merged by Colleagues**: W pull requests
- **Primary Branch**: branch-name
- **Work Duration**: Started at HH:MM, worked for Xh Ym
## 🔨 Commits Today
### Branch: feature/5351-navigation (5 commits)
- `9020cb3` (10:15) ✨ feat(navigation): implement title management and enhance tab system
- `abc1234` (11:30) fix(navigation): resolve routing edge case
- `def5678` (14:45) test(navigation): add comprehensive test coverage
- `ghi9012` (15:20) refactor(navigation): improve code organization
- `jkl3456` (16:00) docs(navigation): update README with usage examples
### Branch: feature/5202-Praemie (2 commits)
- `c208327` (14:23) feat(crm-data-access,checkout): improve primary bonus card selection logic
- `mno7890` (16:45) fix(checkout): handle edge case for bonus points
## 🔀 Merge Activity
### PRs I Merged (as committer)
- **PR #1990**: feat(ui): add new button variants → develop
- **PR #1991**: fix(api): resolve timeout issues → develop
### My PRs Merged by Colleagues
- **PR #1987**: Carousel Library → develop (merged by Nino Righi)
- **PR #1989**: fix(checkout): resolve currency constraint violations → develop (merged by Nino Righi)
### Branch Merges
- `feature/5202-Praemie-stock-info-request-batching``feature/5202-Praemie`
## 🌿 Branch Activity
**Primary Branch**: feature/5351-navigation (5 commits)
**Other Branches**:
- feature/5202-Praemie (2 commits)
- develop (merged 2 PRs)
**Current Branch**: feature/5351-navigation
**Status**: 3 files changed, 2 files staged, 1 file untracked
## 📝 Notes
[Optional section for manual notes - left empty by default]
---
_Report generated on YYYY-MM-DD at HH:MM_
```
**Formatting Rules**:
- Use emoji for section headers (📊 📝 🔨 🔀 🌿)
- Group commits by branch
- Show time for each commit in (HH:MM) format
- Include commit prefixes (feat:, fix:, docs:, etc.)
- Sort branches by number of commits (most active first)
- Highlight primary branch (most commits)
### 6. Save and Display Report
**Objective**: Output report to terminal and save to file
**Display to Terminal**:
- [ ] Print formatted report to stdout
- [ ] Use clear visual separators
- [ ] Ensure easy copy/paste to Slack/Teams/Email
**Save to File**:
- [ ] Create reports directory if it doesn't exist
```bash
mkdir -p reports/eod
```
- [ ] Determine filename
- Format: `reports/eod/YYYY-MM-DD.md`
- Example: `reports/eod/2025-10-28.md`
- [ ] Write report to file
```bash
# Save report
cat > "reports/eod/${TODAY}.md" << 'EOF'
[report content]
EOF
```
- [ ] Provide file location feedback
- Show absolute path to saved file
- Confirm successful save
**If `--save-only` flag**:
- [ ] Skip terminal display
- [ ] Only save to file
- [ ] Show success message with file path
### 7. Provide Summary Statistics
**Objective**: Show quick statistics and next steps
- [ ] Calculate and display:
- Total commits today (excluding PR merge commits)
- Number of branches worked on
- PRs I merged (as committer)
- My PRs merged by colleagues (authored by me, committed by others)
- Work duration (user-specified start time → last commit time)
- Lines of code changed (optional, if available)
- [ ] Suggest next steps:
- Commit uncommitted changes
- Push branches to remote
- Create PR for completed work
- Update task tracking system
## Output Format
### Standard Display
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 End of Day Report - 2025-10-28
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Developer**: Lorenz Hilpert <lorenz@example.com>
**Date**: Monday, October 28, 2025
**Time**: 17:30
---
## 📊 Summary
- **Commits**: 5 commits across 1 branch
- **PRs I Merged**: 2 pull requests (as committer)
- **My PRs Merged by Colleagues**: 0
- **Primary Branch**: feature/5351-navigation
- **Work Duration**: Started at 09:00, worked for 7h 45m (last commit at 16:45)
## 🔨 Commits Today
### Branch: feature/5351-navigation (5 commits)
- `9020cb3` (10:15) ✨ feat(navigation): implement title management and enhance tab system
- `abc1234` (11:30) 🐛 fix(navigation): resolve routing edge case
- `def5678` (14:45) ✅ test(navigation): add comprehensive test coverage
- `ghi9012` (15:20) ♻️ refactor(navigation): improve code organization
- `jkl3456` (16:00) 📝 docs(navigation): update README with usage examples
### Branch: feature/5202-Praemie (2 commits)
- `c208327` (14:23) ✨ feat(crm-data-access,checkout): improve primary bonus card selection logic
- `mno7890` (16:45) 🐛 fix(checkout): handle edge case for bonus points
## 🔀 Merge Activity
### PRs I Merged (as committer)
- **PR #1987**: Carousel Library → develop
- **PR #1989**: fix(checkout): resolve currency constraint violations → develop
### My PRs Merged by Colleagues
_None today_
## 🌿 Branch Activity
**Primary Branch**: feature/5351-navigation (5 commits)
**Other Branches**:
- feature/5202-Praemie (2 commits)
- develop (2 PR merges)
**Current Status**:
- Branch: feature/5351-navigation
- Changes: 3 files changed, 2 files staged, 1 file untracked
- Remote: 5 commits ahead of origin/feature/5351-navigation
## 📝 Notes
_No additional notes_
---
✅ Report saved to: /home/lorenz/Projects/ISA-Frontend/reports/eod/2025-10-28.md
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Daily Statistics
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Commits: 5 (excluding PR merges)
Branches: 1 active branch
PRs I Merged: 2
My PRs Merged by Colleagues: 0
Work Duration: 7h 45m (started at 09:00, last commit at 16:45)
📋 Next Steps
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. ✅ Push feature/5351-navigation to remote
2. ⚠️ Consider creating PR for completed work
3. 💾 1 untracked file - review and commit if needed
```
### No Activity Case
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 End of Day Report - 2025-10-28
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Developer**: Lorenz Hilpert <lorenz@example.com>
**Date**: Monday, October 28, 2025
**Time**: 17:30
---
## 📊 Summary
No commits found for today (2025-10-28).
**Possible Reasons**:
- No development work performed
- Working on uncommitted changes
- Using different git user configuration
**Current Branch**: feature/5351-navigation
**Uncommitted Changes**: 5 files modified, 2 files staged
---
💡 Tip: If you have uncommitted work, commit it before generating the report.
```
### Yesterday's Report
```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 End of Day Report - 2025-10-27 (Yesterday)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Report content for yesterday]
✅ Report saved to: /home/lorenz/Projects/ISA-Frontend/reports/eod/2025-10-27.md
```
## Usage Examples
```bash
# Generate today's EOD report
/eod-report
# Generate yesterday's report (if you forgot)
/eod-report --yesterday
# Generate report for specific date
/eod-report 2025-10-25
# Save to file only (no terminal output)
/eod-report --save-only
# Generate yesterday's report and save only
/eod-report --yesterday --save-only
```
## References
- Git Log Documentation: https://git-scm.com/docs/git-log
- Conventional Commits: https://www.conventionalcommits.org/
- Project Conventions: See CLAUDE.md for commit message standards
- Git Configuration: `git config user.name` and `git config user.email`

View File

@@ -0,0 +1,309 @@
---
allowed-tools: Read, Write, Edit, Bash, Grep
argument-hint: [version] | --since [tag] | --dry-run
description: Generate changelog entries from git tags using Keep a Changelog format
---
# Generate Changelog
Generate changelog entries from git commits between version tags: $ARGUMENTS
## Current State
- Latest Tag: !`git tag --sort=-creatordate | head -n 1`
- CHANGELOG.md: !`test -f CHANGELOG.md && echo "exists" || echo "does not exist"`
- Commits Since Last Tag: !`git log $(git tag --sort=-creatordate | head -n 1)..HEAD --oneline | wc -l`
- Current Branch: !`git branch --show-current`
## Tasks
### 1. Determine Version Range
**Objective**: Identify the commit range for changelog generation
- [ ] Check if version argument provided
- If `[version]` provided: Use as the new version number
- If `--since [tag]` provided: Use custom tag as starting point
- Otherwise: Use latest tag as starting point
```bash
# Find latest tag
LATEST_TAG=$(git tag --sort=-creatordate | head -n 1)
# Get commits since tag
git log ${LATEST_TAG}..HEAD --oneline
# If no tags exist, use entire history
if [ -z "$LATEST_TAG" ]; then
git log --oneline
fi
```
**Edge Cases**:
- No tags exist → Use entire commit history and suggest version 0.1.0
- No commits since last tag → Notify user, no changelog needed
- Invalid tag provided → Error with available tags list
### 2. Extract and Categorize Commits
**Objective**: Parse commit messages and group by Keep a Changelog categories
- [ ] Fetch commits with detailed information
```bash
# Get commits with format: hash | date | message
git log ${LATEST_TAG}..HEAD --pretty=format:"%h|%as|%s" --no-merges
```
- [ ] Parse conventional commit patterns and map to categories:
**Mapping Rules**:
- `feat:` or `feature:`**Added**
- `fix:` or `bugfix:`**Fixed**
- `refactor:`**Changed**
- `perf:` or `performance:`**Changed**
- `docs:`**Changed** (or skip if only documentation)
- `style:`**Changed**
- `test:` → (skip from changelog)
- `chore:` → (skip from changelog)
- `build:` or `ci:` → (skip from changelog)
- `revert:`**Changed** or **Fixed**
- `security:`**Security**
- `deprecate:` or `deprecated:`**Deprecated**
- `remove:` or `breaking:`**Removed**
- Non-conventional commits → **Changed** (default)
- [ ] Extract scope and description from commit messages
**Commit Pattern**: `type(scope): description`
Example:
```
feat(checkout): add reward delivery order support
fix(remission): resolve currency constraint violations
refactor(navigation): implement title management system
```
### 3. Generate Changelog Entry
**Objective**: Create properly formatted changelog section
- [ ] Determine version number
- Use provided `[version]` argument
- Or prompt for new version if not provided
- Format: `[X.Y.Z]` following semantic versioning
- [ ] Get current date in ISO format: `YYYY-MM-DD`
```bash
TODAY=$(date +%Y-%m-%d)
```
- [ ] Build changelog entry following Keep a Changelog format:
```markdown
## [VERSION] - YYYY-MM-DD
### Added
- New feature description from feat: commits
- Another feature
### Changed
- Refactored component description
- Performance improvements
### Deprecated
- Feature marked for removal
### Removed
- Deleted feature or breaking change
### Fixed
- Bug fix description
- Another fix
### Security
- Security improvement description
```
**Rules**:
- Only include sections that have entries
- Sort entries alphabetically within each section
- Use sentence case for descriptions
- Remove commit type prefix from descriptions
- Include scope in parentheses if present: `(scope) description`
- Add reference links to commits/PRs if available
### 4. Update or Preview CHANGELOG.md
**Objective**: Append new entry to changelog file or show preview
**If `--dry-run` flag provided**:
- [ ] Display generated changelog entry to stdout
- [ ] Show preview of where it would be inserted
- [ ] Do NOT modify CHANGELOG.md
- [ ] Exit with success
**Otherwise (append mode)**:
- [ ] Check if CHANGELOG.md exists
- If not, create with standard header:
```markdown
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
```
- [ ] Read existing CHANGELOG.md content
- [ ] Find insertion point (after "## [Unreleased]" section, or after main header)
- [ ] Insert new changelog entry
- [ ] Maintain reverse chronological order (newest first)
- [ ] Write updated content back to CHANGELOG.md
```bash
# Backup existing file
cp CHANGELOG.md CHANGELOG.md.bak
# Insert new entry
# (Implementation handled by Edit tool)
```
### 5. Validate and Report
**Objective**: Verify changelog quality and provide summary
- [ ] Validate generated entry:
- Version format is valid (X.Y.Z)
- Date is correct (YYYY-MM-DD)
- At least one category has entries
- No duplicate entries
- Proper markdown formatting
- [ ] Report statistics:
- Number of commits processed
- Entries per category
- Version number used
- File status (preview/updated)
- [ ] Show next steps:
- Review changelog entry
- Update version in package.json if needed
- Create git tag if appropriate
- Commit changelog changes
## Output Format
### Dry Run Preview
```
🔍 Changelog Preview (--dry-run mode)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## [1.5.0] - 2025-10-28
### Added
- (checkout) Add reward delivery order support
- (navigation) Implement title management and tab system
### Changed
- (carousel) Update carousel library implementation
- (remission) Enhance returns processing workflow
### Fixed
- (checkout) Resolve currency constraint violations in price handling
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Statistics
─────────────
Commits processed: 12
Added: 2 entries
Changed: 2 entries
Fixed: 1 entry
Version: 1.5.0
Date: 2025-10-28
⚠️ This is a preview. Run without --dry-run to update CHANGELOG.md
```
### Append Mode Success
```
✅ Changelog Updated Successfully
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## [1.5.0] - 2025-10-28
### Added
- (checkout) Add reward delivery order support
- (navigation) Implement title management and tab system
### Changed
- (carousel) Update carousel library implementation
- (remission) Enhance returns processing workflow
### Fixed
- (checkout) Resolve currency constraint violations in price handling
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Statistics
─────────────
Commits processed: 12
Added: 2 entries
Changed: 2 entries
Fixed: 1 entry
Version: 1.5.0
File: CHANGELOG.md (updated)
Backup: CHANGELOG.md.bak
📋 Next Steps
─────────────
1. Review the changelog entry in CHANGELOG.md
2. Update version in package.json: npm version 1.5.0
3. Commit the changelog: git add CHANGELOG.md && git commit -m "docs: update changelog for v1.5.0"
4. Create git tag: git tag -a v1.5.0 -m "Release v1.5.0"
5. Push changes: git push && git push --tags
```
### Error Cases
```
❌ No Changes Found
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
No commits found since last tag (v1.4.5).
Nothing to add to changelog.
```
```
❌ No Tags Found
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
No git tags found in this repository.
Suggestions:
- Create your first tag: git tag v0.1.0
- Or specify a commit range: /generate-changelog --since HEAD~10
- Or generate from all commits: /generate-changelog 0.1.0
```
```
⚠️ Invalid Version Format
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Version "1.5" is invalid.
Expected format: X.Y.Z (e.g., 1.5.0)
Please provide a valid semantic version.
```
## References
- Keep a Changelog: https://keepachangelog.com/
- Semantic Versioning: https://semver.org/
- Conventional Commits: https://www.conventionalcommits.org/
- Project Conventions: See CLAUDE.md for commit message standards

188
.claude/commands/quality.md Normal file
View File

@@ -0,0 +1,188 @@
---
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
argument-hint: bundle | coverage [library-name] | --all
description: Analyze code quality: bundle sizes, test coverage, with optimization recommendations
---
# /quality - Code Quality Analysis
Comprehensive quality analysis including bundle sizes and test coverage.
## Subcommands
- `bundle` - Analyze production bundle sizes
- `coverage [library-name]` - Test coverage analysis
- No argument - Run both analyses
- `[library-name]` - Coverage for specific library
## Bundle Analysis
### 1. Run Production Build
```bash
# Clean previous build
rm -rf dist/
# Build for production
npm run build-prod
```
### 2. Analyze Bundle Output
```bash
# List bundle files with sizes
ls -lh dist/apps/isa-app/browser/*.js | awk '{print $9, $5}'
# Get total bundle size
du -sh dist/apps/isa-app/browser/
```
### 3. Identify Large Files
Parse build output and identify:
- Main bundle size
- Lazy-loaded chunk sizes
- Vendor chunks
- Files exceeding thresholds:
- **Warning**: > 2MB
- **Error**: > 5MB
### 4. Analyze Dependencies
```bash
# Check for duplicate dependencies
npm ls --depth=0 | grep -E "UNMET|deduped"
# Show largest node_modules packages
du -sh node_modules/* | sort -rh | head -20
```
### 5. Source Map Analysis (Optional)
```bash
# Install source-map-explorer if needed
npm install -g source-map-explorer
# Analyze main bundle
source-map-explorer dist/apps/isa-app/browser/main.*.js
```
### 6. Bundle Recommendations
**If bundle > 2MB:**
- Identify heavy dependencies to replace or remove
- Suggest lazy loading opportunities
- Check for unused imports
**Code Splitting Opportunities:**
- Large feature modules that could be lazy-loaded
- Heavy libraries that could be dynamically imported
**Dependency Optimization:**
- Replace large libraries with smaller alternatives
- Remove unused dependencies
- Use tree-shakeable imports
---
## Coverage Analysis
### 1. Run Coverage Analysis
```bash
# Single library
npx nx test [library-name] --skip-nx-cache --coverage
# All libraries (if no library specified)
npm run ci # Runs all tests with coverage
```
### 2. Parse Coverage Report
Coverage output in: `coverage/libs/[domain]/[layer]/[name]/`
Extract metrics:
- **Line coverage**: % of executable lines tested
- **Branch coverage**: % of conditional branches tested
- **Function coverage**: % of functions called in tests
- **Statement coverage**: % of statements executed
### 3. Identify Uncovered Code
Parse coverage report to find:
- **Uncovered files**: Files with 0% coverage
- **Partially covered files**: < 80% coverage
- **Uncovered lines**: Specific line numbers not tested
- **Uncovered branches**: Conditional paths not tested
### 4. Categorize Coverage Gaps
**Critical (High Risk):**
- Service methods handling business logic
- Data transformation functions
- Error handling code paths
- Security-related functions
- State management store actions
**Important (Medium Risk):**
- Component public methods
- Utility functions
- Validators and guards
**Low Priority:**
- Getters/setters
- Simple property assignments
### 5. Generate Recommendations
For each coverage gap provide:
- **File and line numbers**
- **Risk level** (Critical/Important/Low)
- **Suggested test type** (unit/integration)
- **Test approach** (example test scenario)
---
## Output Formats
### Bundle Report
```
Bundle Analysis Report
======================
Total Size: X.XX MB [STATUS]
Main Bundle: X.XX MB
Largest Chunks:
- chunk-name.js: X.XX MB
Largest Dependencies:
1. dependency-name: X.XX MB
Recommendations:
- [Prioritized action items]
```
### Coverage Report
```
Coverage Summary for [library-name]
====================================
Line Coverage: XX.X% (XXX/XXX lines)
Branch Coverage: XX.X% (XXX/XXX branches)
Function Coverage: XX.X% (XXX/XXX functions)
Target: 80% (Recommended minimum)
Status: [Met/Below Target/Critical]
Files Needing Attention:
[Categorized list with priorities]
Top Priority Tests to Add:
[Prioritized recommendations]
```
## Error Handling
- **Build failures**: Show error and suggest fixes
- **Missing tools**: Offer to install (source-map-explorer)
- **No coverage data**: Ensure `--coverage` flag used
- **Missing library**: Verify library name is correct
## References
- CLAUDE.md Build Configuration section
- docs/guidelines/testing.md
- Angular build optimization: https://angular.dev/tools/cli/build
- Vitest coverage: https://vitest.dev/guide/coverage

View File

@@ -1,129 +0,0 @@
# /quality:bundle-analyze - Analyze Bundle Sizes
Analyze production bundle sizes and provide optimization recommendations. Project thresholds: 2MB warning, 5MB error.
## Tasks
### 1. Run Production Build
```bash
# Clean previous build
rm -rf dist/
# Build for production
npm run build-prod
```
### 2. Analyze Bundle Output
```bash
# List bundle files with sizes
ls -lh dist/apps/isa-app/browser/*.js | awk '{print $9, $5}'
# Get total bundle size
du -sh dist/apps/isa-app/browser/
```
### 3. Identify Large Files
Parse build output and identify:
- Main bundle size
- Lazy-loaded chunk sizes
- Vendor chunks
- Files exceeding thresholds:
- **Warning**: > 2MB
- **Error**: > 5MB
### 4. Analyze Dependencies
```bash
# Check for duplicate dependencies
npm ls --depth=0 | grep -E "UNMET|deduped"
# Show largest node_modules packages
du -sh node_modules/* | sort -rh | head -20
```
### 5. Source Map Analysis
Use source maps to identify large contributors:
```bash
# Install source-map-explorer if needed
npm install -g source-map-explorer
# Analyze main bundle
source-map-explorer dist/apps/isa-app/browser/main.*.js
```
### 6. Generate Recommendations
Based on analysis, provide actionable recommendations:
**If bundle > 2MB:**
- Identify heavy dependencies to replace or remove
- Suggest lazy loading opportunities
- Check for unused imports
**Code Splitting Opportunities:**
- Large feature modules that could be lazy-loaded
- Heavy libraries that could be dynamically imported
- Vendor code that could be split into separate chunks
**Dependency Optimization:**
- Replace large libraries with smaller alternatives
- Remove unused dependencies
- Use tree-shakeable imports
**Build Configuration:**
- Enable/optimize compression
- Check for source maps in production (should be disabled)
- Verify optimization flags
### 7. Comparative Analysis
If previous build data exists:
```bash
# Compare with previous build
# (Requires manual tracking or CI/CD integration)
echo "Current build: $(du -sh dist/apps/isa-app/browser/ | awk '{print $1}')"
```
### 8. Generate Report
Create formatted report with:
- Total bundle size with threshold status (✅ < 2MB, ⚠️ 2-5MB, ❌ > 5MB)
- Main bundle and largest chunks
- Top 10 largest dependencies
- Optimization recommendations prioritized by impact
- Lazy loading opportunities
## Output Format
```
Bundle Analysis Report
======================
Total Size: X.XX MB [STATUS]
Main Bundle: X.XX MB
Largest Chunks:
- chunk-name.js: X.XX MB
- ...
Largest Dependencies:
1. dependency-name: X.XX MB
...
Recommendations:
🔴 Critical (> 5MB):
- [Action items]
⚠️ Warning (2-5MB):
- [Action items]
✅ Optimization Opportunities:
- [Action items]
Lazy Loading Candidates:
- [Feature modules]
```
## Error Handling
- Build failures: Show error and suggest fixes
- Missing tools: Offer to install (source-map-explorer)
- No dist folder: Run build first
## References
- CLAUDE.md Build Configuration section
- Angular build optimization: https://angular.dev/tools/cli/build
- package.json (build-prod script)

View File

@@ -1,201 +0,0 @@
# /quality:coverage - Generate Test Coverage Report
Generate comprehensive test coverage report with recommendations for improving coverage.
## Parameters
- `library-name` (optional): Specific library to analyze. If omitted, analyzes all libraries.
## Tasks
### 1. Run Coverage Analysis
```bash
# Single library
npx nx test [library-name] --skip-nx-cache --coverage
# All libraries (if no library specified)
npm run ci # Runs all tests with coverage
```
### 2. Parse Coverage Report
Coverage output typically in:
- `coverage/libs/[domain]/[layer]/[name]/`
- Look for `coverage-summary.json` or text output
Extract metrics:
- **Line coverage**: % of executable lines tested
- **Branch coverage**: % of conditional branches tested
- **Function coverage**: % of functions called in tests
- **Statement coverage**: % of statements executed
### 3. Identify Uncovered Code
Parse coverage report to find:
- **Uncovered files**: Files with 0% coverage
- **Partially covered files**: < 80% coverage
- **Uncovered lines**: Specific line numbers not tested
- **Uncovered branches**: Conditional paths not tested
```bash
# List files with coverage below 80%
# (Parse from coverage JSON output)
```
### 4. Categorize Coverage Gaps
**Critical (High Risk):**
- Service methods handling business logic
- Data transformation functions
- Error handling code paths
- Security-related functions
- State management store actions
**Important (Medium Risk):**
- Component public methods
- Utility functions
- Validators
- Pipes and filters
- Guard functions
**Low Priority:**
- Getters/setters
- Simple property assignments
- Console logging
- Type definitions
### 5. Generate Recommendations
For each coverage gap, provide:
- **File and line numbers**
- **Risk level** (Critical/Important/Low)
- **Suggested test type** (unit/integration)
- **Test approach** (example test scenario)
Example:
```
📍 libs/oms/data-access/src/lib/services/order.service.ts:45-52
🔴 Critical - Business Logic
❌ 0% coverage - Error handling path
Recommended test:
it('should handle API error when fetching order', async () => {
// Mock API to return error
// Call method
// Verify error handling
});
```
### 6. Calculate Coverage Trends
If historical data available:
- Compare with previous coverage percentage
- Show improvement/regression
- Identify files with declining coverage
### 7. Generate HTML Report
```bash
# Open coverage report in browser (if available)
open coverage/libs/[domain]/[layer]/[name]/index.html
```
### 8. Create Coverage Summary Report
**Overall Metrics:**
```
Coverage Summary for [library-name]
====================================
Line Coverage: XX.X% (XXX/XXX lines)
Branch Coverage: XX.X% (XXX/XXX branches)
Function Coverage: XX.X% (XXX/XXX functions)
Statement Coverage: XX.X% (XXX/XXX statements)
Target: 80% (Recommended minimum)
Status: ✅ Met / ⚠️ Below Target / 🔴 Critical
```
**Files Needing Attention:**
```
🔴 Critical (< 50% coverage):
1. service-name.service.ts - 35% (business logic)
2. data-processor.ts - 42% (transformations)
⚠️ Below Target (50-79% coverage):
3. component-name.component.ts - 68%
4. validator.ts - 72%
✅ Well Covered (≥ 80% coverage):
- Other files maintaining good coverage
```
**Top Priority Tests to Add:**
1. [File:Line] - [Description] - [Risk Level]
2. ...
### 9. Framework-Specific Notes
**Vitest:**
- Coverage provider: v8 or istanbul
- Config in `vitest.config.ts`
- Coverage thresholds configurable
**Jest:**
- Coverage collected via `--coverage` flag
- Config in `jest.config.ts`
- Coverage directory: `coverage/`
### 10. Set Coverage Thresholds (Optional)
Suggest adding to test config:
```typescript
// vitest.config.ts
coverage: {
thresholds: {
lines: 80,
functions: 80,
branches: 80,
statements: 80
}
}
```
## Output Format
```
Test Coverage Report
====================
Library: [name]
Test Framework: [Vitest/Jest]
Generated: [timestamp]
📊 Coverage Metrics
-------------------
Lines: XX.X% ████████░░ (XXX/XXX)
Branches: XX.X% ███████░░░ (XXX/XXX)
Functions: XX.X% █████████░ (XXX/XXX)
Statements: XX.X% ████████░░ (XXX/XXX)
🎯 Target: 80% | Status: [✅/⚠️/🔴]
🔍 Coverage Gaps
----------------
[Categorized list with priorities]
💡 Recommendations
------------------
[Prioritized list of tests to add]
📈 Next Steps
-------------
1. Focus on critical coverage gaps first
2. Add tests for business logic in [files]
3. Consider setting coverage thresholds
4. Re-run: npx nx test [library-name] --skip-nx-cache --coverage
```
## Error Handling
- No coverage data: Ensure `--coverage` flag used
- Missing library: Verify library name is correct
- Coverage tool not configured: Check test config for coverage setup
## References
- docs/guidelines/testing.md
- CLAUDE.md Testing Framework section
- Vitest coverage: https://vitest.dev/guide/coverage
- Jest coverage: https://jestjs.io/docs/configuration#collectcoverage-boolean

View File

@@ -0,0 +1,106 @@
---
allowed-tools: Read, Write, Edit, Bash
argument-hint: [doc-type] | --implementation | --api | --architecture | --sync | --validate
description: Systematically update project documentation with implementation status, API changes, and synchronized content
---
# Documentation Update & Synchronization
Update project documentation systematically: $ARGUMENTS
## Current Documentation State
- Documentation structure: !`find . -name "*.md" | head -10`
- Specs directory: @specs/ (if exists)
- Implementation status: !`grep -r "✅\|❌\|⚠️" docs/ specs/ 2>/dev/null | wc -l` status indicators
- Recent changes: !`git log --oneline --since="1 week ago" -- "*.md" | head -5`
- Project progress: @CLAUDE.md or @README.md (if exists)
## Task
## Documentation Analysis
1. Review current documentation status:
- Check `specs/implementation_status.md` for overall project status
- Review implemented phase document (`specs/phase{N}_implementation_plan.md`)
- Review `specs/flutter_structurizr_implementation_spec.md` and `specs/flutter_structurizr_implementation_spec_updated.md`
- Review `specs/testing_plan.md` to ensure it is current given recent test passes, failures, and changes
- Examine `CLAUDE.md` and `README.md` for project-wide documentation
- Check for and document any new lessons learned or best practices in CLAUDE.md
2. Analyze implementation and testing results:
- Review what was implemented in the last phase
- Review testing results and coverage
- Identify new best practices discovered during implementation
- Note any implementation challenges and solutions
- Cross-reference updated documentation with recent implementation and test results to ensure accuracy
## Documentation Updates
1. Update phase implementation document:
- Mark completed tasks with ✅ status
- Update implementation percentages
- Add detailed notes on implementation approach
- Document any deviations from original plan with justification
- Add new sections if needed (lessons learned, best practices)
- Document specific implementation details for complex components
- Include a summary of any new troubleshooting tips or workflow improvements discovered during the phase
2. Update implementation status document:
- Update phase completion percentages
- Add or update implementation status for components
- Add notes on implementation approach and decisions
- Document best practices discovered during implementation
- Note any challenges overcome and solutions implemented
3. Update implementation specification documents:
- Mark completed items with ✅ or strikethrough but preserve original requirements
- Add notes on implementation details where appropriate
- Add references to implemented files and classes
- Update any implementation guidance based on experience
4. Update CLAUDE.md and README.md if necessary:
- Add new best practices
- Update project status
- Add new implementation guidance
- Document known issues or limitations
- Update usage examples to include new functionality
5. Document new testing procedures:
- Add details on test files created
- Include test running instructions
- Document test coverage
- Explain testing approach for complex components
## Documentation Formatting and Structure
1. Maintain consistent documentation style:
- Use clear headings and sections
- Include code examples where helpful
- Use status indicators (✅, ⚠️, ❌) consistently
- Maintain proper Markdown formatting
2. Ensure documentation completeness:
- Cover all implemented features
- Include usage examples
- Document API changes or additions
- Include troubleshooting guidance for common issues
## Guidelines
- DO NOT CREATE new specification files
- UPDATE existing files in the `specs/` directory
- Maintain consistent documentation style
- Include practical examples where appropriate
- Cross-reference related documentation sections
- Document best practices and lessons learned
- Provide clear status updates on project progress
- Update numerical completion percentages
- Ensure documentation reflects actual implementation
Provide a summary of documentation updates after completion, including:
1. Files updated
2. Major changes to documentation
3. Updated completion percentages
4. New best practices documented
5. Status of the overall project after this phase

View File

@@ -0,0 +1,417 @@
---
name: angular-effects-alternatives
description: This skill should be used when writing Angular code with signals and effects. Use when deciding whether to use effect(), computed(), or reactive patterns for state management. Applies to all Angular components and services using signals, especially when considering effect() for state propagation, data synchronization, or reactive flows. Essential for code review of effect usage and refactoring imperative patterns to declarative alternatives.
---
# Angular Effects Alternatives
## Overview
This skill guides proper usage of Angular's `effect()` and provides declarative alternatives for common patterns. Effects are frequently misused for state propagation, leading to circular updates, maintenance issues, and violations of reactive principles. This skill prevents anti-patterns and promotes maintainable, declarative code.
## When to Use Effects (Valid Use Cases)
Effects are **primarily for rendering content that cannot be rendered through data binding**. Valid use cases are limited to:
### 1. Logging
Recording application events or debugging:
```typescript
effect(() => {
const error = this.error();
if (error) {
console.error('Error occurred:', error);
}
});
```
### 2. Canvas Painting
Custom graphics rendering (e.g., Angular Three library, Chart.js integration):
```typescript
effect(() => {
const data = this.chartData();
this.renderCanvas(data);
});
```
### 3. Custom DOM Behavior
Imperative APIs that require direct DOM manipulation:
```typescript
effect(() => {
const message = this.notificationMessage();
if (message) {
this.snackBar.open(message, 'Close');
}
});
```
**Key principle:** Data binding is the preferred way to display data. Effects should only be used when data binding is insufficient.
## Understanding Auto-Tracking
Angular automatically tracks signals accessed during effect execution, **even within called methods**:
```typescript
effect(() => {
this.logError(); // Signal tracking happens inside this method
});
logError(): void {
const error = this.error(); // This signal is automatically tracked
if (error) {
console.error(error);
}
}
```
**Implication:** Auto-tracking makes effect dependencies non-obvious and hard to maintain. This is a primary reason to avoid effects for state management.
## When NOT to Use Effects (Anti-Patterns)
### ❌ Anti-Pattern 1: State Propagation
**NEVER use effects to propagate state changes to other state:**
```typescript
// ❌ WRONG - Anti-pattern
effect(() => {
const value = this.source();
this.derived.set(value * 2);
});
```
**Problems:**
- Risk of circular updates and infinite loops
- Hard to maintain due to implicit tracking
- Violates declarative reactive principles
- Inappropriate glitch-free semantics
### ❌ Anti-Pattern 2: Synchronizing Signals
```typescript
// ❌ WRONG - Anti-pattern
effect(() => {
const filter = this.filter();
this.loadData(filter);
});
```
### ❌ Anti-Pattern 3: Event Emulation
```typescript
// ❌ WRONG - Anti-pattern
effect(() => {
const count = this.itemCount();
this.countChanged.emit(count);
});
```
**Why signals ≠ events:** Signals are designed to be glitch-free, collapsing multiple updates. This makes them inappropriate for representing discrete events.
## Decision Tree: Effect vs Alternative
```
Need to react to signal changes?
├─ Synchronous derivation?
│ └─ ✅ Use computed()
├─ Asynchronous derivation?
│ └─ ✅ Use Resource API
├─ Complex reactive flow with race conditions?
│ └─ ✅ Use RxJS (toObservable + operators + toSignal)
├─ Event-based trigger (not state change)?
│ └─ ✅ React to event directly, not signal
├─ Need RxJS operators with signals?
│ └─ ✅ Use reactive helpers (rxMethod, deriveAsync)
└─ Rendering non-data-bound content (logging, canvas, imperative API)?
└─ ✅ Use effect()
```
## Recommended Alternatives
### Alternative 1: Use `computed()` for Synchronous Derivations
**When to use:** Deriving new state synchronously from existing signals.
```typescript
// ✅ CORRECT - Declarative
const derived = computed(() => {
return this.baseSignal() * 2;
});
const fullName = computed(() => {
return `${this.firstName()} ${this.lastName()}`;
});
```
**Benefits:**
- Declarative and maintainable
- Automatic dependency tracking
- Memoized and efficient
- No risk of circular updates
### Alternative 2: Use Resource API for Asynchronous Derivations
**When to use:** Loading data based on reactive parameters.
```typescript
// ✅ CORRECT - Declarative async state
readonly itemsResource = resource({
params: this.filter,
loader: ({ params, abortSignal }) => {
return this.dataService.load(params, abortSignal);
}
});
readonly items = computed(() => this.itemsResource.value() ?? []);
```
**Benefits:**
- Automatic race condition handling
- Built-in loading/error states
- Declarative parameter tracking
- Cancellation support
**See also:** `ngrx-resource-api` skill for detailed Resource API patterns.
### Alternative 3: React to Events, Not State Changes
**When to use:** User interactions or DOM events should trigger actions.
```typescript
// ❌ WRONG - Reacting to signal change
effect(() => {
const searchTerm = this.searchTerm();
this.search(searchTerm);
});
// ✅ CORRECT - React to event
<input (input)="search($event.target.value)" />
// Component
search(term: string): void {
this.searchTerm.set(term);
this.performSearch(term);
}
```
**Benefits:**
- Clear causality (event → action)
- No auto-tracking complexity
- Explicit control flow
### Alternative 4: RxJS Integration
**When to use:** Complex reactive flows requiring operators like `debounceTime`, `switchMap`, `combineLatest`.
```typescript
// ✅ CORRECT - RxJS for complex flows
readonly searchTerm = signal('');
readonly searchTerm$ = toObservable(this.searchTerm);
readonly results$ = this.searchTerm$.pipe(
debounceTime(300),
distinctUntilChanged(),
switchMap(term => this.searchService.search(term))
);
readonly results = toSignal(this.results$, { initialValue: [] });
```
**Benefits:**
- Full RxJS operator ecosystem
- Race condition prevention (`switchMap`)
- Powerful composition
- Type-safe streams
**Pattern:** Signal → Observable (toObservable) → RxJS operators → Signal (toSignal)
### Alternative 5: Reactive Helpers
**When to use:** Need RxJS operators but prefer signal-centric API.
#### Using `rxMethod` (NgRx Signal Store)
```typescript
readonly loadItem = rxMethod<number>(
pipe(
tap(() => patchState(this, { loading: true })),
switchMap(id => this.service.findById(id)),
tap(item => patchState(this, { item, loading: false }))
)
);
// Call with signal or value
constructor() {
this.loadItem(this.selectedId);
}
```
#### Using `deriveAsync` (ngxtension)
```typescript
readonly data = deriveAsync(() => {
const filter = this.filter();
return this.service.load(filter);
});
```
**Benefits:**
- Signal-friendly API
- RxJS operator support
- Cleaner than manual Observable conversion
- Automatic subscription management
## The `explicitEffect` Consideration
Some libraries provide `explicitEffect` to restrict auto-tracking:
```typescript
// Uses untracked() internally to limit tracking
explicitEffect(this.id, (id) => {
this.store.load(id);
});
```
**Evaluation:**
- ✅ Mitigates auto-tracking drawbacks
- ✅ Makes dependencies explicit
- ❌ Still imperative (not declarative)
- ❌ Doesn't solve circular update risks
- ❌ Less idiomatic than reactive alternatives
**Recommendation:** Prefer declarative patterns (computed, Resource API, RxJS) over `explicitEffect`.
## Common Refactoring Patterns
### Pattern 1: Effect for State Sync → computed()
```typescript
// ❌ Before
effect(() => {
const x = this.x();
const y = this.y();
this.sum.set(x + y);
});
// ✅ After
readonly sum = computed(() => this.x() + this.y());
```
### Pattern 2: Effect for Async Load → Resource API
```typescript
// ❌ Before
effect(() => {
const id = this.selectedId();
this.loadItem(id);
});
// ✅ After
readonly itemResource = resource({
params: this.selectedId,
loader: ({ params }) => this.service.loadItem(params)
});
```
### Pattern 3: Effect for Debounced Search → RxJS
```typescript
// ❌ Before
effect(() => {
const term = this.searchTerm();
// No way to debounce within effect
this.search(term);
});
// ✅ After
readonly searchTerm$ = toObservable(this.searchTerm);
readonly results = toSignal(
this.searchTerm$.pipe(
debounceTime(300),
switchMap(term => this.searchService.search(term))
),
{ initialValue: [] }
);
```
### Pattern 4: Effect for Event Notification → Direct Event Handling
```typescript
// ❌ Before
effect(() => {
const value = this.value();
this.valueChange.emit(value);
});
// ✅ After
updateValue(newValue: string): void {
this.value.set(newValue);
this.valueChange.emit(newValue);
}
```
## Code Review Checklist
When reviewing code with `effect()`, ask:
- [ ] Is this for rendering non-data-bound content? (logging, canvas, imperative APIs)
- **YES:** Effect is appropriate
- **NO:** Continue checklist
- [ ] Is this synchronous state derivation?
- **YES:** Use `computed()` instead
- [ ] Is this asynchronous data loading?
- **YES:** Use Resource API instead
- [ ] Does this need RxJS operators (debounce, switchMap, etc.)?
- **YES:** Use RxJS integration or reactive helpers instead
- [ ] Is this reacting to a user event?
- **YES:** Handle event directly instead
- [ ] Could this cause circular updates?
- **YES:** Refactor immediately - this will cause bugs
## Anti-Pattern Detection Rules
Flag any effect that:
1. **Calls `set()` or `update()` on signals** - Likely state propagation anti-pattern
2. **Calls service methods that update state** - Hidden state propagation
3. **Emits events based on signal changes** - Signal/event semantic mismatch
4. **Has try/catch for async operations** - Should use Resource API
5. **Would benefit from debouncing/throttling** - Should use RxJS
## Migration Strategy
When converting effects to alternatives:
1. **Identify effect purpose** - State derivation? Async load? Event handling?
2. **Choose appropriate alternative** - Use decision tree above
3. **Implement replacement** - Follow patterns in this skill
4. **Test thoroughly** - Ensure reactive flow works correctly
5. **Remove effect** - Clean up unused code
## Key Principles
1. **Effects are for side effects, not state management**
2. **Prefer declarative over imperative**
3. **Use computed() for sync, Resource API for async**
4. **React to events, not state changes**
5. **RxJS for complex reactive flows**
6. **Auto-tracking is powerful but opaque - avoid when possible**
## When in Doubt
Ask: "Can the user see this without an effect using data binding?"
- **YES:** Don't use effect, use data binding
- **NO:** Effect might be appropriate (but verify against decision tree)

View File

@@ -0,0 +1,240 @@
---
name: angular-template
description: This skill should be used when writing or reviewing Angular component templates. It provides guidance on modern Angular 20+ template syntax including control flow (@if, @for, @switch, @defer), content projection (ng-content), template references (ng-template, ng-container), variable declarations (@let), and expression binding. Use when creating components, refactoring to modern syntax, implementing lazy loading, or reviewing template best practices.
---
# Angular Template
Guide for modern Angular 20+ template patterns: control flow, lazy loading, projection, and binding.
## When to Use
- Creating/reviewing component templates
- Refactoring legacy `*ngIf/*ngFor/*ngSwitch` to modern syntax
- Implementing `@defer` lazy loading
- Designing reusable components with `ng-content`
- Template performance optimization
**Related Skills:** These skills work together when writing Angular templates:
- **[html-template](../html-template/SKILL.md)** - E2E testing attributes (`data-what`, `data-which`) and ARIA accessibility
- **[tailwind](../tailwind/SKILL.md)** - ISA design system styling (colors, typography, spacing, layout)
- **[logging](../logging/SKILL.md)** - MANDATORY logging in all Angular files using `@isa/core/logging`
## Control Flow (Angular 17+)
### @if / @else if / @else
```typescript
@if (user.isAdmin()) {
<app-admin-dashboard />
} @else if (user.isEditor()) {
<app-editor-dashboard />
} @else {
<app-viewer-dashboard />
}
// Store result with 'as'
@if (user.profile?.settings; as settings) {
<p>Theme: {{settings.theme}}</p>
}
```
### @for with @empty
```typescript
@for (product of products(); track product.id) {
<app-product-card [product]="product" />
} @empty {
<p>No products available</p>
}
```
**CRITICAL:** Always provide `track` expression:
- Best: `track item.id` or `track item.uuid`
- Static lists: `track $index`
- **NEVER:** `track identity(item)` (causes full re-render)
**Contextual variables:** `$count`, `$index`, `$first`, `$last`, `$even`, `$odd`
### @switch
```typescript
@switch (viewMode()) {
@case ('grid') { <app-grid-view /> }
@case ('list') { <app-list-view /> }
@default { <app-grid-view /> }
}
```
## @defer Lazy Loading
### Basic Usage
```typescript
@defer (on viewport) {
<app-heavy-chart />
} @placeholder (minimum 500ms) {
<div class="skeleton"></div>
} @loading (after 100ms; minimum 1s) {
<mat-spinner />
} @error {
<p>Failed to load</p>
}
```
### Triggers
| Trigger | Use Case |
|---------|----------|
| `idle` (default) | Non-critical features |
| `viewport` | Below-the-fold content |
| `interaction` | User-initiated (click/keydown) |
| `hover` | Tooltips/popovers |
| `timer(Xs)` | Delayed content |
| `when(expr)` | Custom condition |
**Multiple triggers:** `@defer (on interaction; on timer(5s))`
**Prefetching:** `@defer (on interaction; prefetch on idle)`
### Requirements
- Components **MUST be standalone**
- No `@ViewChild`/`@ContentChild` references
- Reserve space in `@placeholder` to prevent layout shift
### Best Practices
- ✅ Defer below-the-fold content
- ❌ Never defer above-the-fold (harms LCP)
- ❌ Avoid `immediate`/`timer` during initial render (harms TTI)
- Test with network throttling
## Content Projection
### Single Slot
```typescript
@Component({
selector: 'ui-card',
template: `<div class="card"><ng-content></ng-content></div>`
})
```
### Multi-Slot with Selectors
```typescript
@Component({
template: `
<header><ng-content select="card-header"></ng-content></header>
<main><ng-content select="card-body"></ng-content></main>
<footer><ng-content></ng-content></footer> <!-- default slot -->
`
})
```
**Usage:**
```html
<ui-card>
<card-header><h3>Title</h3></card-header>
<card-body><p>Content</p></card-body>
<button>Action</button> <!-- goes to default slot -->
</ui-card>
```
**Fallback content:** `<ng-content select="title">Default Title</ng-content>`
**Aliasing:** `<h3 ngProjectAs="card-header">Title</h3>`
### CRITICAL Constraint
`ng-content` **always instantiates** (even if hidden). For conditional projection, use `ng-template` + `NgTemplateOutlet`.
## Template References
### ng-template
```html
<ng-template #userCard let-user="userData" let-index="i">
<div class="user">#{{index}}: {{user.name}}</div>
</ng-template>
<ng-container
*ngTemplateOutlet="userCard; context: {userData: currentUser(), i: 0}">
</ng-container>
```
**Access in component:**
```typescript
myTemplate = viewChild<TemplateRef<unknown>>('myTemplate');
```
### ng-container
Groups elements without DOM footprint:
```html
<p>
Hero's name is
<ng-container @if="hero()">{{hero().name}}</ng-container>.
</p>
```
## Variables
### @let (Angular 18.1+)
```typescript
@let userName = user().name;
@let greeting = 'Hello, ' + userName;
@let asyncData = data$ | async;
<h1>{{greeting}}</h1>
```
**Scoped to current view** (not hoisted to parent/sibling).
### Template References (#)
```html
<input #emailInput type="email" />
<button (click)="sendEmail(emailInput.value)">Send</button>
<app-datepicker #startDate />
<button (click)="startDate.open()">Open</button>
```
## Binding Patterns
**Property:** `[disabled]="!isValid()"`
**Attribute:** `[attr.aria-label]="label()"` `[attr.data-what]="'card'"`
**Event:** `(click)="save()"` `(input)="onInput($event)"`
**Two-way:** `[(ngModel)]="userName"`
**Class:** `[class.active]="isActive()"` or `[class]="{active: isActive()}"`
**Style:** `[style.width.px]="width()"` or `[style]="{color: textColor()}"`
## Best Practices
1. **Use signals:** `isExpanded = signal(false)`
2. **Prefer control flow over directives:** Use `@if` not `*ngIf`
3. **Keep expressions simple:** Use `computed()` for complex logic
4. **Testing & Accessibility:** Always add E2E and ARIA attributes (see **[html-template](../html-template/SKILL.md)** skill)
5. **Track expressions:** Required in `@for`, use unique IDs
## Migration
| Legacy | Modern |
|--------|--------|
| `*ngIf="condition"` | `@if (condition) { }` |
| `*ngFor="let item of items"` | `@for (item of items; track item.id) { }` |
| `[ngSwitch]` | `@switch (value) { @case ('a') { } }` |
**CLI migration:** `ng generate @angular/core:control-flow`
## Reference Files
For detailed examples and edge cases, see:
- `references/control-flow-reference.md` - @if/@for/@switch patterns
- `references/defer-patterns.md` - Lazy loading strategies
- `references/projection-patterns.md` - Advanced ng-content
- `references/template-reference.md` - ng-template/ng-container
Search with: `grep -r "pattern" references/`

View File

@@ -0,0 +1,185 @@
# Control Flow Reference
Advanced patterns for `@if`, `@for`, `@switch`.
## @if Patterns
### Store Results with `as`
```typescript
@if (user.profile?.settings?.theme; as theme) {
<p>Theme: {{theme}}</p>
}
@if (data$ | async; as data) {
<app-list [items]="data.items" />
}
```
### Complex Conditions
```typescript
@if (isAdmin() && hasPermission('edit')) {
<button (click)="edit()">Edit</button>
}
@if (user()?.role === 'admin' || user()?.role === 'moderator') {
<app-moderation-panel />
}
```
## @for Patterns
### Contextual Variables
```typescript
@for (user of users(); track user.id) {
<tr [class.odd]="$odd">
<td>{{$index + 1}}</td>
<td>{{user.name}}</td>
<td>{{$count}} total</td>
@if ($first) { <span>First</span> }
</tr>
}
```
### Track Strategies
```typescript
// ✅ Best: Unique ID
@for (order of orders(); track order.uuid) { }
// ✅ Good: Composite key
@for (item of items(); track item.categoryId + '-' + item.id) { }
// ⚠️ OK: Index (static only)
@for (color of ['red', 'blue']; track $index) { }
// ❌ NEVER: Identity function
@for (item of items(); track identity(item)) { }
```
### Nested Loops
```typescript
@for (category of categories(); track category.id) {
<div class="category">
<h3>{{category.name}}</h3>
@for (product of category.products; track product.id) {
<app-product [product]="product" [categoryIdx]="$index" />
}
</div>
}
```
### Filter in Component
```typescript
// Component
activeUsers = computed(() => this.users().filter(u => u.isActive));
// Template
@for (user of activeUsers(); track user.id) {
<app-user-card [user]="user" />
} @empty {
<p>No active users</p>
}
```
## @switch Patterns
### Basic Switch
```typescript
@switch (viewMode()) {
@case ('grid') { <app-grid-view /> }
@case ('list') { <app-list-view /> }
@case ('table') { <app-table-view /> }
@default { <app-grid-view /> }
}
```
### Nested Switch
```typescript
@switch (category()) {
@case ('electronics') {
@switch (subcategory()) {
@case ('phones') { <app-phone-list /> }
@case ('laptops') { <app-laptop-list /> }
@default { <app-electronics-list /> }
}
}
@case ('clothing') { <app-clothing-list /> }
@default { <app-all-categories /> }
}
```
### Combined with Other Control Flow
```typescript
@switch (status()) {
@case ('loading') { <mat-spinner /> }
@case ('success') {
@if (data()?.length) {
@for (item of data(); track item.id) {
<app-item [item]="item" />
}
} @else {
<p>No data</p>
}
}
@case ('error') { <app-error [message]="errorMessage()" /> }
}
```
## Common Patterns
### Loading State
```typescript
@if (isLoading()) {
<mat-spinner />
} @else if (error()) {
<app-error [error]="error()" (retry)="loadData()" />
} @else {
@for (item of items(); track item.id) {
<app-item [item]="item" />
} @empty {
<app-empty-state />
}
}
```
### Tab Navigation
```typescript
<nav>
@for (tab of tabs(); track tab.id) {
<button [class.active]="activeTab() === tab.id" (click)="setActiveTab(tab.id)">
{{tab.label}}
</button>
}
</nav>
@switch (activeTab()) {
@case ('profile') { <app-profile /> }
@case ('settings') { <app-settings /> }
@default { <app-profile /> }
}
```
### Hierarchical Data
```typescript
@for (section of sections(); track section.id) {
<details [open]="section.isExpanded">
<summary>{{section.title}} ({{section.items.length}})</summary>
@for (item of section.items; track item.id) {
<div>{{item.name}}</div>
} @empty {
<p>No items</p>
}
</details>
}
```

View File

@@ -0,0 +1,301 @@
# @defer Patterns
Lazy loading strategies and performance optimization.
## Basic Patterns
### Complete State Management
```typescript
@defer (on viewport) {
<app-product-reviews [productId]="productId()" />
} @placeholder (minimum 500ms) {
<div class="skeleton" style="height: 400px;"></div>
} @loading (after 100ms; minimum 1s) {
<mat-spinner />
} @error {
<p>Failed to load reviews</p>
<button (click)="retry()">Retry</button>
}
```
## Triggers
### Common Strategies
```typescript
// Idle: Non-critical features
@defer (on idle) { <app-recommendations /> }
// Viewport: Below-the-fold
@defer (on viewport) { <app-comments /> }
// Interaction: User-initiated
@defer (on interaction) { <app-filters /> }
// Hover: Tooltips/popovers
@defer (on hover) { <app-user-tooltip /> }
// Timer: Delayed content
@defer (on timer(3s)) { <app-promo-banner /> }
// When: Custom condition
@defer (when userLoggedIn()) { <app-personalized-content /> }
```
### Multiple Triggers
```typescript
// OR logic: first trigger wins
@defer (on interaction; on timer(5s)) {
<app-newsletter-signup />
}
```
### Prefetching
```typescript
// Load JS on idle, show on interaction
@defer (on interaction; prefetch on idle) {
<app-video-player />
}
// Load JS on hover, show on click
@defer (on interaction; prefetch on hover) {
<app-modal />
}
```
## Performance Patterns
### Bundle Size Reduction
```typescript
<div class="product-page">
<!-- Critical: Load immediately -->
<app-product-header [product]="product()" />
<!-- Heavy chart: Defer on viewport -->
@defer (on viewport) {
<app-analytics-chart />
} @placeholder {
<div style="height: 300px;"></div>
}
<!-- Video player: Defer on interaction -->
@defer (on interaction; prefetch on idle) {
<app-video-player />
} @placeholder {
<img [src]="videoThumbnail" />
}
</div>
```
### Staggered Loading
```typescript
<div class="dashboard">
<app-header /> <!-- Immediate -->
@defer (on idle) {
<app-key-metrics /> <!-- Important -->
}
@defer (on viewport) {
<app-recent-activity /> <!-- Secondary -->
} @placeholder {
<div style="height: 400px;"></div>
}
@defer (on viewport) {
<app-analytics /> <!-- Tertiary -->
} @placeholder {
<div style="height: 300px;"></div>
}
</div>
```
### Conditional Defer (Mobile Only)
```typescript
// Component
shouldDefer = computed(() => this.breakpoint([Breakpoint.Tablet]));
// Template
@if (shouldDefer()) {
@defer (on viewport) { <app-heavy-chart /> }
} @else {
<app-heavy-chart />
}
```
## Requirements
### Must Be Standalone
```typescript
// ✅ Valid
@Component({ standalone: true })
export class ChartComponent {}
@defer { <app-chart /> } // Will defer
// ❌ Invalid
@NgModule({ declarations: [ChartComponent] })
@defer { <app-chart /> } // Won't defer! Loads eagerly
```
### No External References
```typescript
// ❌ Invalid: ViewChild reference
@ViewChild('chart') chart!: ChartComponent;
@defer { <app-chart #chart /> } // ERROR
// ✅ Valid: Use events
@defer {
<app-chart (dataLoaded)="onChartLoaded($event)" />
}
```
## Core Web Vitals
### Prevent Layout Shift (CLS)
```typescript
// ✅ Reserve exact height
@defer (on viewport) {
<app-large-component />
} @placeholder {
<div style="height: 600px;"></div>
}
// ❌ No height reserved
@defer (on viewport) {
<app-large-component />
} @placeholder {
<p>Loading...</p> // Causes layout shift
}
```
### Don't Defer LCP Elements
```typescript
// ❌ BAD: Hero image deferred
@defer (on idle) {
<img src="hero.jpg" /> <!-- LCP element! -->
}
// ✅ GOOD: Load immediately
<img src="hero.jpg" />
@defer (on viewport) {
<app-below-fold-content />
}
```
### Improve Time to Interactive (TTI)
```typescript
// Critical: Immediate
<button (click)="addToCart()">Add to Cart</button>
// Non-critical: Defer
@defer (on idle) {
<app-social-share />
}
```
## Common Pitfalls
### 1. Cascading Defer (Bad)
```typescript
// ❌ Sequential loads
@defer (on idle) {
<div>
@defer (on idle) {
<div>
@defer (on idle) { <app-nested /> }
</div>
}
</div>
}
// ✅ Single defer
@defer (on idle) {
<div><div><app-nested /></div></div>
}
```
### 2. Above-Fold Defer
```typescript
// ❌ Above-fold content deferred
<header>
@defer (on idle) {
<nav>...</nav> <!-- Should load immediately -->
}
</header>
// ✅ Below-fold only
<header><nav>...</nav></header>
<main>
@defer (on viewport) {
<app-below-fold />
}
</main>
```
### 3. Missing Minimum Durations
```typescript
// ❌ Flickers quickly
@defer {
<app-fast-component />
} @loading {
<mat-spinner /> <!-- Flashes briefly -->
}
// ✅ Smooth loading
@defer {
<app-fast-component />
} @loading (after 100ms; minimum 500ms) {
<mat-spinner />
}
```
## Real-World Example
```typescript
<div class="product-page">
<!-- Critical: Immediate -->
<app-product-header />
<app-product-images />
<app-add-to-cart />
<!-- Important: Idle -->
@defer (on idle) {
<app-product-description />
}
<!-- Below fold: Viewport -->
@defer (on viewport) {
<app-reviews />
} @placeholder {
<div style="min-height: 400px;"></div>
}
<!-- Optional: Interaction -->
@defer (on interaction; prefetch on idle) {
<app-size-guide />
} @placeholder {
<button>View Size Guide</button>
}
<!-- Related: Viewport -->
@defer (on viewport) {
<app-related-products />
}
</div>
```

View File

@@ -0,0 +1,253 @@
# Content Projection Patterns
Advanced `ng-content`, `ng-template`, and `ng-container` techniques.
## Basic Projection
### Single Slot
```typescript
@Component({
selector: 'ui-panel',
template: `<div class="panel"><ng-content></ng-content></div>`
})
export class PanelComponent {}
```
### Multi-Slot with Selectors
```typescript
@Component({
selector: 'ui-card',
template: `
<header><ng-content select="card-header"></ng-content></header>
<main><ng-content select="card-body"></ng-content></main>
<footer><ng-content></ng-content></footer> <!-- default -->
`
})
```
**Usage:**
```html
<ui-card>
<card-header><h3>Title</h3></card-header>
<card-body><p>Content</p></card-body>
<button>Action</button> <!-- default slot -->
</ui-card>
```
**Selectors:** Element (`card-title`), class (`.actions`), attribute (`[slot='footer']`)
**Fallback:** `<ng-content select="title">Default</ng-content>`
**Aliasing:** `<h3 ngProjectAs="card-header">Title</h3>`
## Conditional Projection
`ng-content` always instantiates (even if hidden). Use `ng-template` for truly conditional content:
```typescript
@Component({
selector: 'ui-expandable',
imports: [NgTemplateOutlet],
template: `
<div (click)="toggle()">
<ng-content select="header"></ng-content>
<span>{{ isExpanded() ? '▼' : '▶' }}</span>
</div>
@if (isExpanded()) {
<ng-container *ngTemplateOutlet="contentTemplate()"></ng-container>
}
`
})
export class ExpandableComponent {
isExpanded = signal(false);
contentTemplate = contentChild<TemplateRef<unknown>>('content');
toggle() { this.isExpanded.update(v => !v); }
}
```
**Usage:**
```html
<ui-expandable>
<header><h3>Click to expand</h3></header>
<ng-template #content>
<app-heavy-component /> <!-- Only rendered when expanded -->
</ng-template>
</ui-expandable>
```
## Template-Based Projection
### Accepting Template Fragments
```typescript
@Component({
selector: 'ui-list',
imports: [NgTemplateOutlet],
template: `
<ul>
@for (item of items(); track item.id) {
<li>
<ng-container
*ngTemplateOutlet="itemTemplate(); context: { $implicit: item, index: $index }">
</ng-container>
</li>
}
</ul>
`
})
export class ListComponent<T> {
items = input.required<T[]>();
itemTemplate = contentChild.required<TemplateRef<{ $implicit: T; index: number }>>('itemTemplate');
}
```
**Usage:**
```html
<ui-list [items]="users()">
<ng-template #itemTemplate let-user let-i="index">
<div>{{i + 1}}. {{user.name}}</div>
</ng-template>
</ui-list>
```
### Multiple Template Slots
```typescript
@Component({
selector: 'ui-data-table',
imports: [NgTemplateOutlet],
template: `
<table>
<thead><ng-container *ngTemplateOutlet="headerTemplate()"></ng-container></thead>
<tbody>
@for (row of data(); track row.id) {
<ng-container *ngTemplateOutlet="rowTemplate(); context: { $implicit: row }"></ng-container>
}
</tbody>
<tfoot><ng-container *ngTemplateOutlet="footerTemplate()"></ng-container></tfoot>
</table>
`
})
export class DataTableComponent<T> {
data = input.required<T[]>();
headerTemplate = contentChild.required<TemplateRef<void>>('header');
rowTemplate = contentChild.required<TemplateRef<{ $implicit: T }>>('row');
footerTemplate = contentChild<TemplateRef<void>>('footer');
}
```
## Querying Projected Content
### Using ContentChildren
```typescript
@Component({
selector: 'ui-tabs',
template: `
<nav>
@for (tab of tabs(); track tab.id) {
<button [class.active]="tab === activeTab()" (click)="selectTab(tab)">
{{tab.label()}}
</button>
}
</nav>
<ng-content></ng-content>
`
})
export class TabsComponent {
tabs = contentChildren(TabComponent);
activeTab = signal<TabComponent | null>(null);
ngAfterContentInit() {
this.selectTab(this.tabs()[0]);
}
selectTab(tab: TabComponent) {
this.tabs().forEach(t => t.isActive.set(false));
tab.isActive.set(true);
this.activeTab.set(tab);
}
}
@Component({
selector: 'ui-tab',
template: `@if (isActive()) { <ng-content></ng-content> }`
})
export class TabComponent {
label = input.required<string>();
isActive = signal(false);
id = Math.random().toString(36);
}
```
## Real-World Examples
### Modal/Dialog
```typescript
@Component({
selector: 'ui-modal',
imports: [NgTemplateOutlet],
template: `
@if (isOpen()) {
<div class="backdrop" (click)="close()">
<div class="modal" (click)="$event.stopPropagation()">
<header>
<ng-content select="modal-title"></ng-content>
<button (click)="close()">×</button>
</header>
<main><ng-content></ng-content></main>
<footer>
<ng-content select="modal-actions">
<button (click)="close()">Close</button>
</ng-content>
</footer>
</div>
</div>
}
`
})
export class ModalComponent {
isOpen = signal(false);
open() { this.isOpen.set(true); }
close() { this.isOpen.set(false); }
}
```
### Form Field Wrapper
```typescript
@Component({
selector: 'ui-form-field',
template: `
<div class="form-field" [class.has-error]="error()">
<label [for]="fieldId()">
<ng-content select="field-label"></ng-content>
@if (required()) { <span class="required">*</span> }
</label>
<div class="input-wrapper"><ng-content></ng-content></div>
@if (error()) { <span class="error">{{error()}}</span> }
@if (hint()) { <span class="hint">{{hint()}}</span> }
</div>
`
})
export class FormFieldComponent {
fieldId = input.required<string>();
required = input(false);
error = input<string>();
hint = input<string>();
}
```
## Performance Notes
- `ng-content` **always instantiates** projected content
- For conditional projection, use `ng-template` + `NgTemplateOutlet`
- Projected content evaluates in **parent component context**
- Use `computed()` for expensive expressions in projected content
## Common Pitfalls
1. **Using ng-content in structural directives:** Won't work as expected. Use `ng-template` instead.
2. **Forgetting default slot:** Unmatched content disappears without default `<ng-content></ng-content>`
3. **Template order matters:** Content renders in template order, not usage order

View File

@@ -0,0 +1,304 @@
# ng-template and ng-container Reference
Template fragments and grouping elements.
## ng-template Basics
### Creating Fragments
```html
<ng-template #myFragment>
<h3>Template content</h3>
<p>Not rendered until explicitly instantiated</p>
</ng-template>
```
### Rendering with NgTemplateOutlet
```typescript
import { NgTemplateOutlet } from '@angular/common';
@Component({
imports: [NgTemplateOutlet],
template: `
<ng-template #greeting><h1>Hello</h1></ng-template>
<ng-container *ngTemplateOutlet="greeting"></ng-container>
`
})
```
### Passing Context
```html
<ng-template #userCard let-user="user" let-index="idx">
<div>#{{index}}: {{user.name}}</div>
</ng-template>
<ng-container
*ngTemplateOutlet="userCard; context: {user: currentUser(), idx: 0}">
</ng-container>
```
**$implicit for default parameter:**
```html
<ng-template #simple let-value>
<p>{{value}}</p>
</ng-template>
<ng-container *ngTemplateOutlet="simple; context: {$implicit: 'Hello'}">
</ng-container>
```
## Accessing Templates
### ViewChild
```typescript
@Component({
template: `
<ng-template #myTemplate><p>Content</p></ng-template>
<button (click)="render()">Render</button>
`
})
export class MyComponent {
myTemplate = viewChild<TemplateRef<unknown>>('myTemplate');
viewContainer = inject(ViewContainerRef);
render() {
this.viewContainer.createEmbeddedView(this.myTemplate()!);
}
}
```
### ContentChild
```typescript
@Component({
selector: 'ui-dialog',
template: `<ng-container *ngTemplateOutlet="contentTemplate()"></ng-container>`
})
export class DialogComponent {
contentTemplate = contentChild<TemplateRef<unknown>>('content');
}
```
**Usage:**
```html
<ui-dialog>
<ng-template #content>
<h2>Dialog Content</h2>
</ng-template>
</ui-dialog>
```
## Programmatic Rendering
### ViewContainerRef
```typescript
@Component({
template: `
<ng-template #dynamic let-title>
<h2>{{title}}</h2>
</ng-template>
<button (click)="addView()">Add</button>
`
})
export class DynamicComponent {
dynamic = viewChild<TemplateRef<{ $implicit: string }>>('dynamic');
viewContainer = inject(ViewContainerRef);
views: EmbeddedViewRef<any>[] = [];
addView() {
const view = this.viewContainer.createEmbeddedView(
this.dynamic()!,
{ $implicit: `View ${this.views.length + 1}` }
);
this.views.push(view);
}
}
```
### Custom Directive
```typescript
@Directive({ selector: '[appDynamicHost]', standalone: true })
export class DynamicHostDirective {
viewContainer = inject(ViewContainerRef);
render(template: TemplateRef<any>, context?: any) {
this.viewContainer.clear();
this.viewContainer.createEmbeddedView(template, context);
}
}
```
## ng-container Patterns
Groups elements without DOM node:
```html
<!-- Without extra wrapper -->
<p>
Hero's name is
<ng-container @if="hero()">{{hero().name}}</ng-container>.
</p>
```
### Use Cases
**1. Structural directives without wrappers:**
```html
<div>
<ng-container @if="showSection()">
<h2>Title</h2>
<p>Content</p>
</ng-container>
</div>
```
**2. Grouping multiple elements:**
```html
<ul>
@for (category of categories(); track category.id) {
<ng-container>
<li class="header">{{category.name}}</li>
@for (item of category.items; track item.id) {
<li>{{item.name}}</li>
}
</ng-container>
}
</ul>
```
**3. Conditional options:**
```html
<select [(ngModel)]="value">
@for (group of groups(); track group.id) {
<optgroup [label]="group.label">
@for (opt of group.options; track opt.id) {
<ng-container @if="opt.isEnabled">
<option [value]="opt.value">{{opt.label}}</option>
</ng-container>
}
</optgroup>
}
</select>
```
**4. Template outlets:**
```html
<div>
<ng-container *ngTemplateOutlet="header()"></ng-container>
<main><ng-container *ngTemplateOutlet="content()"></ng-container></main>
<ng-container *ngTemplateOutlet="footer()"></ng-container>
</div>
```
**5. ViewContainerRef injection:**
```typescript
@Directive({ selector: '[appDynamic]', standalone: true })
export class DynamicDirective {
viewContainer = inject(ViewContainerRef); // Injects at ng-container
}
```
```html
<ng-container appDynamic></ng-container>
```
## Advanced Patterns
### Reusable Repeater
```typescript
@Component({
selector: 'ui-repeater',
imports: [NgTemplateOutlet],
template: `
@for (item of items(); track trackBy(item)) {
<ng-container
*ngTemplateOutlet="itemTemplate(); context: { $implicit: item, index: $index }">
</ng-container>
}
`
})
export class RepeaterComponent<T> {
items = input.required<T[]>();
itemTemplate = contentChild.required<TemplateRef<{ $implicit: T; index: number }>>('item');
trackBy = input<(item: T) => any>((item: any) => item);
}
```
### Template Polymorphism
```typescript
@Component({
selector: 'ui-card-list',
imports: [NgTemplateOutlet],
template: `
@for (item of items(); track item.id) {
@switch (item.type) {
@case ('product') {
<ng-container *ngTemplateOutlet="productTpl(); context: { $implicit: item }"></ng-container>
}
@case ('service') {
<ng-container *ngTemplateOutlet="serviceTpl(); context: { $implicit: item }"></ng-container>
}
@default {
<ng-container *ngTemplateOutlet="defaultTpl(); context: { $implicit: item }"></ng-container>
}
}
}
`
})
export class CardListComponent {
items = input.required<Item[]>();
productTpl = contentChild.required<TemplateRef<{ $implicit: Item }>>('product');
serviceTpl = contentChild.required<TemplateRef<{ $implicit: Item }>>('service');
defaultTpl = contentChild.required<TemplateRef<{ $implicit: Item }>>('default');
}
```
## Context Scoping
Templates evaluate in **declaration context**, not render context:
```typescript
@Component({
selector: 'parent',
template: `
<ng-template #tpl>
<p>{{parentValue()}}</p> <!-- Evaluates in parent -->
</ng-template>
<child [template]="tpl"></child>
`
})
export class ParentComponent {
parentValue = signal('Parent');
}
@Component({
selector: 'child',
imports: [NgTemplateOutlet],
template: `<ng-container *ngTemplateOutlet="template()"></ng-container>`
})
export class ChildComponent {
template = input.required<TemplateRef<void>>();
}
```
**Override with context:**
```typescript
<ng-container
*ngTemplateOutlet="template(); context: { childData: childValue() }">
</ng-container>
```
## Common Pitfalls
1. **Forgetting context:** `<ng-container *ngTemplateOutlet="tpl"></ng-container>` without context won't pass data
2. **Styling ng-container:** Not in DOM, can't be styled
3. **Template timing:** Access templates in `ngAfterViewInit`, not constructor
4. **Confusing ng-template vs ng-content:** Template = reusable fragment, Content = projects parent content

View File

@@ -1,6 +1,6 @@
---
name: api-change-analyzer
description: This skill should be used when analyzing Swagger/OpenAPI specification changes BEFORE regenerating API clients. It compares old vs new specs, categorizes changes as breaking/compatible/warnings, finds affected code, and generates migration strategies. Use this skill when the user wants to check API changes safely before sync, mentions "check breaking changes", or needs impact assessment.
description: This skill should be used when checking for breaking changes before API regeneration, assessing backend API update impact, or user mentions "check breaking changes", "API diff", "impact assessment". Analyzes Swagger/OpenAPI spec changes, categorizes as breaking/compatible/warnings, and provides migration strategies.
---
# API Change Analyzer

View File

@@ -0,0 +1,171 @@
---
name: architecture-documentation
description: Generate architecture documentation (C4, Arc42, ADRs, PlantUML). Auto-invoke when user mentions "architecture docs", "C4 model", "ADR", "document architecture", "system design", or "create architecture diagram".
---
# Architecture Documentation Skill
Generate comprehensive architecture documentation using modern frameworks and best practices.
## When to Use
- Creating or updating architecture documentation
- Generating C4 model diagrams (Context, Container, Component, Code)
- Writing Architecture Decision Records (ADRs)
- Documenting system design and component relationships
- Creating PlantUML or Mermaid diagrams
## Available Frameworks
### C4 Model
Best for: Visualizing software architecture at different abstraction levels
Levels:
1. **Context** - System landscape and external actors
2. **Container** - High-level technology choices (apps, databases, etc.)
3. **Component** - Internal structure of containers
4. **Code** - Class/module level detail (optional)
See: `@references/c4-model.md` for patterns and examples
### Arc42 Template
Best for: Comprehensive architecture documentation
Sections:
1. Introduction and Goals
2. Constraints
3. Context and Scope
4. Solution Strategy
5. Building Block View
6. Runtime View
7. Deployment View
8. Cross-cutting Concepts
9. Architecture Decisions
10. Quality Requirements
11. Risks and Technical Debt
12. Glossary
See: `@references/arc42.md` for template structure
### Architecture Decision Records (ADRs)
Best for: Documenting individual architectural decisions
See: `@references/adr-template.md` for format and examples
## Workflow
### 1. Discovery Phase
```bash
# Find existing architecture files
find . -name "*architecture*" -o -name "*.puml" -o -name "*.mmd"
# Identify service boundaries
cat nx.json docker-compose.yml
# Check for existing ADRs
ls -la docs/adr/ docs/decisions/
```
### 2. Analysis Phase
- Analyze codebase structure (`libs/`, `apps/`)
- Identify dependencies from `tsconfig.base.json` paths
- Review service boundaries from `project.json` tags
- Map data flow from API definitions
### 3. Documentation Phase
Based on the request, create appropriate documentation:
**For C4 diagrams:**
```
docs/architecture/
├── c4-context.puml
├── c4-container.puml
└── c4-component-[name].puml
```
**For ADRs:**
```
docs/adr/
├── 0001-record-architecture-decisions.md
├── 0002-[decision-title].md
└── template.md
```
**For Arc42:**
```
docs/architecture/
└── arc42/
├── 01-introduction.md
├── 02-constraints.md
└── ...
```
## ISA-Frontend Specific Context
### Monorepo Structure
- **apps/**: Angular applications
- **libs/**: Shared libraries organized by domain
- `libs/[domain]/feature/` - Feature modules
- `libs/[domain]/data-access/` - State management
- `libs/[domain]/ui/` - Presentational components
- `libs/[domain]/util/` - Utilities
### Key Architectural Patterns
- **Nx Monorepo** with strict module boundaries
- **NgRx Signal Store** for state management
- **Standalone Components** (Angular 20+)
- **Domain-Driven Design** library organization
### Documentation Locations
- ADRs: `docs/adr/`
- Architecture diagrams: `docs/architecture/`
- API documentation: Generated from Swagger/OpenAPI
## Output Standards
### PlantUML Format
```plantuml
@startuml C4_Context
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Context.puml
Person(user, "User", "System user")
System(system, "ISA System", "Main application")
System_Ext(external, "External API", "Third-party service")
Rel(user, system, "Uses")
Rel(system, external, "Calls")
@enduml
```
### Mermaid Format
```mermaid
graph TD
A[User] --> B[ISA App]
B --> C[API Gateway]
C --> D[Backend Services]
```
### ADR Format
```markdown
# ADR-XXXX: [Title]
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[What is the issue?]
## Decision
[What was decided?]
## Consequences
[What are the results?]
```
## Best Practices
1. **Start with Context** - Always begin with C4 Level 1 (System Context)
2. **Use Consistent Notation** - Stick to one diagramming tool/format
3. **Keep ADRs Atomic** - One decision per ADR
4. **Version Control** - Commit documentation with code changes
5. **Review Regularly** - Architecture docs decay; schedule reviews

View File

@@ -0,0 +1,213 @@
# Architecture Decision Record (ADR) Template
## Overview
Architecture Decision Records document significant architectural decisions along with their context and consequences.
## ADR Format
### Standard Template
```markdown
# ADR-XXXX: [Short Title]
## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-YYYY]
## Date
YYYY-MM-DD
## Context
What is the issue that we're seeing that is motivating this decision or change?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
### Positive
- Benefit 1
- Benefit 2
### Negative
- Drawback 1
- Drawback 2
### Neutral
- Side effect 1
## Alternatives Considered
### Option 1: [Name]
- Pros: ...
- Cons: ...
- Why rejected: ...
### Option 2: [Name]
- Pros: ...
- Cons: ...
- Why rejected: ...
## References
- [Link to related documentation]
- [Link to discussion thread]
```
## Example ADRs
### ADR-0001: Use Nx Monorepo
```markdown
# ADR-0001: Use Nx Monorepo for Project Organization
## Status
Accepted
## Date
2024-01-15
## Context
The ISA Frontend consists of multiple applications and shared libraries. We need a way to:
- Share code between applications
- Maintain consistent tooling and dependencies
- Enable efficient CI/CD with affected-based testing
- Enforce architectural boundaries
## Decision
We will use Nx as our monorepo tool with the following structure:
- `apps/` - Deployable applications
- `libs/` - Shared libraries organized by domain and type
## Consequences
### Positive
- Single version of dependencies across all projects
- Affected-based testing reduces CI time
- Consistent tooling (ESLint, Prettier, TypeScript)
- Built-in dependency graph visualization
### Negative
- Learning curve for team members new to Nx
- More complex initial setup
- All code in single repository increases clone time
### Neutral
- Requires discipline in library boundaries
- Need to maintain `project.json` and tags
## Alternatives Considered
### Polyrepo
- Pros: Simpler individual repos, independent deployments
- Cons: Dependency management nightmare, code duplication
- Why rejected: Too much overhead for code sharing
```
### ADR-0002: Adopt NgRx Signal Store
```markdown
# ADR-0002: Adopt NgRx Signal Store for State Management
## Status
Accepted
## Date
2024-03-01
## Context
We need a state management solution that:
- Integrates well with Angular signals
- Provides predictable state updates
- Supports devtools for debugging
- Has good TypeScript support
## Decision
We will use NgRx Signal Store for new features and gradually migrate existing stores.
## Consequences
### Positive
- Native signal integration
- Simpler boilerplate than classic NgRx
- Better performance with fine-grained reactivity
- Excellent TypeScript inference
### Negative
- Migration effort for existing NgRx stores
- Different patterns from classic NgRx
### Neutral
- Team needs to learn new API
## Alternatives Considered
### Classic NgRx (Store + Effects)
- Pros: Mature, well-documented
- Cons: Verbose boilerplate, doesn't leverage signals
- Why rejected: Signal Store is the future direction
### Akita
- Pros: Less boilerplate
- Cons: Not Angular-native, less community support
- Why rejected: NgRx has better Angular integration
```
## ADR Naming Convention
```
docs/adr/
├── 0000-adr-template.md # Template file
├── 0001-use-nx-monorepo.md
├── 0002-adopt-ngrx-signal-store.md
├── 0003-standalone-components.md
└── README.md # Index of all ADRs
```
## ADR Index Template
```markdown
# Architecture Decision Records
This directory contains Architecture Decision Records (ADRs) for the ISA Frontend.
## Index
| ADR | Title | Status | Date |
|-----|-------|--------|------|
| [0001](0001-use-nx-monorepo.md) | Use Nx Monorepo | Accepted | 2024-01-15 |
| [0002](0002-adopt-ngrx-signal-store.md) | Adopt NgRx Signal Store | Accepted | 2024-03-01 |
| [0003](0003-standalone-components.md) | Migrate to Standalone Components | Accepted | 2024-04-01 |
## Process
1. Copy `0000-adr-template.md` to `XXXX-short-title.md`
2. Fill in the template
3. Submit PR for review
4. Update status once decided
5. Update this index
```
## Best Practices
1. **One decision per ADR** - Keep ADRs focused
2. **Number sequentially** - Never reuse numbers
3. **Record context** - Why was this needed?
4. **Document alternatives** - Show what was considered
5. **Keep concise** - 1-2 pages max
6. **Update status** - Mark deprecated decisions
7. **Link related ADRs** - Reference superseding decisions
8. **Review regularly** - Quarterly ADR review meetings
## When to Write an ADR
Write an ADR when:
- Choosing a framework or library
- Defining code organization patterns
- Setting up infrastructure
- Establishing conventions
- Making trade-offs that affect multiple teams
Don't write an ADR for:
- Small implementation details
- Obvious choices with no alternatives
- Temporary solutions

View File

@@ -0,0 +1,268 @@
# Arc42 Architecture Documentation Template
## Overview
Arc42 is a template for architecture documentation with 12 sections covering all aspects of software architecture.
## Template Structure
### 1. Introduction and Goals
```markdown
# 1. Introduction and Goals
## 1.1 Requirements Overview
- Core business requirements driving the architecture
- Key functional requirements
- Quality goals and priorities
## 1.2 Quality Goals
| Priority | Quality Goal | Description |
|----------|-------------|-------------|
| 1 | Performance | < 200ms response time |
| 2 | Usability | Intuitive for store employees |
| 3 | Reliability | 99.9% uptime during store hours |
## 1.3 Stakeholders
| Role | Expectations |
|------|-------------|
| Store Employee | Fast, reliable daily operations |
| IT Operations | Easy deployment and monitoring |
| Development Team | Maintainable, testable code |
```
### 2. Architecture Constraints
```markdown
# 2. Architecture Constraints
## 2.1 Technical Constraints
| Constraint | Background |
|------------|------------|
| Angular 20+ | Company standard frontend framework |
| TypeScript strict | Type safety requirement |
| Browser support | Chrome 90+, Edge 90+ |
## 2.2 Organizational Constraints
| Constraint | Background |
|------------|------------|
| Monorepo | Nx-based shared codebase |
| CI/CD | Azure DevOps pipelines |
| Code review | All changes require PR approval |
## 2.3 Conventions
- Conventional commits
- ESLint/Prettier formatting
- Component-driven development
```
### 3. System Scope and Context
```markdown
# 3. System Scope and Context
## 3.1 Business Context
[C4 Level 1 - System Context Diagram]
| Neighbor | Description |
|----------|-------------|
| Store Employee | Primary user performing daily operations |
| Backend APIs | Provides business logic and data |
| Printer Service | Label and receipt printing |
## 3.2 Technical Context
[Deployment/Network Diagram]
| Interface | Protocol | Description |
|-----------|----------|-------------|
| REST API | HTTPS/JSON | Backend communication |
| WebSocket | WSS | Real-time updates |
| OAuth2 | HTTPS | Authentication |
```
### 4. Solution Strategy
```markdown
# 4. Solution Strategy
## Key Architectural Decisions
| Decision | Rationale |
|----------|-----------|
| Angular SPA | Rich interactive UI, offline capability |
| NgRx Signal Store | Predictable state management |
| Nx Monorepo | Code sharing, consistent tooling |
| Standalone Components | Better tree-shaking, simpler imports |
## Quality Achievement Strategies
| Quality Goal | Approach |
|--------------|----------|
| Performance | Lazy loading, caching, code splitting |
| Maintainability | Domain-driven library structure |
| Testability | Component isolation, dependency injection |
```
### 5. Building Block View
```markdown
# 5. Building Block View
## Level 1: Application Overview
[C4 Container Diagram]
## Level 2: Domain Decomposition
| Domain | Purpose | Libraries |
|--------|---------|-----------|
| CRM | Customer management | crm-feature-*, crm-data-access-* |
| OMS | Order management | oms-feature-*, oms-data-access-* |
| Checkout | Transactions | checkout-feature-*, checkout-data-access-* |
## Level 3: Feature Details
[C4 Component Diagrams per domain]
```
### 6. Runtime View
```markdown
# 6. Runtime View
## Scenario 1: User Login
```mermaid
sequenceDiagram
User->>App: Open application
App->>Auth: Redirect to login
Auth->>App: Return token
App->>API: Fetch user profile
API->>App: User data
App->>User: Display dashboard
```
## Scenario 2: Order Processing
[Sequence diagram for order flow]
```
### 7. Deployment View
```markdown
# 7. Deployment View
## Infrastructure
```mermaid
graph TD
CDN[CDN] --> Browser[User Browser]
Browser --> LB[Load Balancer]
LB --> API[API Gateway]
API --> Services[Backend Services]
```
## Environments
| Environment | URL | Purpose |
|-------------|-----|---------|
| Development | dev.isa.local | Local development |
| Staging | staging.isa.com | Integration testing |
| Production | isa.com | Live system |
```
### 8. Cross-cutting Concepts
```markdown
# 8. Cross-cutting Concepts
## 8.1 Domain Model
[Domain entity relationships]
## 8.2 Security
- Authentication: OAuth2/OIDC
- Authorization: Role-based access control
- Data protection: HTTPS, encrypted storage
## 8.3 Error Handling
- Global error interceptor
- User-friendly error messages
- Error logging to backend
## 8.4 Logging
- @isa/core/logging library
- Structured log format
- Log levels: trace, debug, info, warn, error
```
### 9. Architecture Decisions
```markdown
# 9. Architecture Decisions
See [ADR folder](../adr/) for detailed decision records.
## Key Decisions
- ADR-0001: Use Nx Monorepo
- ADR-0002: Adopt NgRx Signal Store
- ADR-0003: Migrate to Standalone Components
```
### 10. Quality Requirements
```markdown
# 10. Quality Requirements
## Quality Tree
```
Quality
├── Performance
│ ├── Response Time < 200ms
│ └── Time to Interactive < 3s
├── Reliability
│ ├── Uptime 99.9%
│ └── Graceful degradation
└── Maintainability
├── Test coverage > 80%
└── Clear module boundaries
```
## Quality Scenarios
| Scenario | Measure | Target |
|----------|---------|--------|
| Page load | Time to interactive | < 3s |
| API call | Response time | < 200ms |
| Build | CI pipeline duration | < 10min |
```
### 11. Risks and Technical Debt
```markdown
# 11. Risks and Technical Debt
## Identified Risks
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| Backend unavailable | Medium | High | Offline mode |
| Performance degradation | Low | Medium | Monitoring |
## Technical Debt
| Item | Priority | Effort |
|------|----------|--------|
| Legacy Jest tests | Medium | High |
| Any types in codebase | High | Medium |
```
### 12. Glossary
```markdown
# 12. Glossary
| Term | Definition |
|------|------------|
| ADR | Architecture Decision Record |
| C4 | Context, Container, Component, Code model |
| ISA | In-Store Application |
| SPA | Single Page Application |
```
## Best Practices
1. **Start with sections 1-4** - Goals, constraints, context, strategy
2. **Add diagrams to section 5** - Building block views
3. **Document decisions in section 9** - Link to ADRs
4. **Keep updated** - Review quarterly
5. **Use templates** - Consistent formatting

View File

@@ -0,0 +1,163 @@
# C4 Model Reference
## Overview
The C4 model provides a way to visualize software architecture at four levels of abstraction:
1. **Context** - System landscape
2. **Container** - Applications and data stores
3. **Component** - Internal structure
4. **Code** - Class/module detail (optional)
## Level 1: System Context Diagram
Shows the system under design and its relationships with users and external systems.
### PlantUML Template
```plantuml
@startuml C4_Context
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Context.puml
LAYOUT_WITH_LEGEND()
title System Context Diagram - ISA Frontend
Person(user, "Store Employee", "Uses the ISA application")
Person(admin, "Administrator", "Manages system configuration")
System(isa, "ISA Frontend", "Angular application for in-store operations")
System_Ext(backend, "ISA Backend", "REST API services")
System_Ext(auth, "Auth Provider", "Authentication service")
System_Ext(printer, "Printer Service", "Receipt/label printing")
Rel(user, isa, "Uses", "Browser")
Rel(admin, isa, "Configures", "Browser")
Rel(isa, backend, "API calls", "HTTPS/JSON")
Rel(isa, auth, "Authenticates", "OAuth2")
Rel(isa, printer, "Prints", "WebSocket")
@enduml
```
### Key Elements
- **Person**: Human users of the system
- **System**: The system being documented (highlighted)
- **System_Ext**: External systems the system depends on
- **Rel**: Relationships between elements
## Level 2: Container Diagram
Shows the high-level technology choices and how containers communicate.
### PlantUML Template
```plantuml
@startuml C4_Container
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Container.puml
LAYOUT_WITH_LEGEND()
title Container Diagram - ISA Frontend
Person(user, "Store Employee")
System_Boundary(isa, "ISA Frontend") {
Container(spa, "SPA", "Angular 20", "Single-page application")
Container(pwa, "Service Worker", "Workbox", "Offline capability")
ContainerDb(storage, "Local Storage", "IndexedDB", "Offline data cache")
}
System_Ext(api, "ISA API Gateway")
System_Ext(cdn, "CDN", "Static assets")
Rel(user, spa, "Uses", "Browser")
Rel(spa, pwa, "Registers")
Rel(pwa, storage, "Caches data")
Rel(spa, api, "API calls", "REST/JSON")
Rel(spa, cdn, "Loads assets", "HTTPS")
@enduml
```
### Container Types
- **Container**: Application or service
- **ContainerDb**: Database or data store
- **ContainerQueue**: Message queue
## Level 3: Component Diagram
Shows the internal structure of a container.
### PlantUML Template
```plantuml
@startuml C4_Component
!include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Component.puml
LAYOUT_WITH_LEGEND()
title Component Diagram - OMS Feature Module
Container_Boundary(oms, "OMS Feature") {
Component(list, "Order List", "Angular Component", "Displays orders")
Component(detail, "Order Detail", "Angular Component", "Order management")
Component(store, "Order Store", "NgRx Signal Store", "State management")
Component(api, "Order API Service", "Angular Service", "API communication")
}
ContainerDb_Ext(backend, "OMS Backend API")
Rel(list, store, "Reads state")
Rel(detail, store, "Reads/writes state")
Rel(store, api, "Fetches data")
Rel(api, backend, "HTTP requests")
@enduml
```
## ISA-Frontend Domain Components
### Suggested Component Structure
```
libs/[domain]/
├── feature/ → Component diagrams
│ └── [feature]/
├── data-access/ → Store/API components
│ └── [store]/
├── ui/ → Presentational components
│ └── [component]/
└── util/ → Utility components
└── [util]/
```
### Domain Boundaries
- **CRM**: Customer management, loyalty
- **OMS**: Order management, returns
- **Checkout**: Payment, transactions
- **Remission**: Product returns processing
- **Catalogue**: Product information
## Mermaid Alternative
```mermaid
C4Context
title System Context - ISA Frontend
Person(user, "Store Employee", "Daily operations")
System(isa, "ISA Frontend", "Angular SPA")
System_Ext(backend, "Backend Services")
System_Ext(auth, "Auth Service")
Rel(user, isa, "Uses")
Rel(isa, backend, "API calls")
Rel(isa, auth, "Authenticates")
```
## Best Practices
1. **One diagram per level** - Don't mix abstraction levels
2. **Consistent naming** - Use same names across diagrams
3. **Show key relationships** - Not every possible connection
4. **Include legends** - Explain notation
5. **Keep it simple** - 5-20 elements per diagram max

View File

@@ -1,6 +1,6 @@
---
name: architecture-enforcer
description: This skill should be used when validating import boundaries and architectural rules in the ISA-Frontend monorepo. It checks for circular dependencies, layer violations (Feature→Feature), domain violations (OMS→Remission), and relative imports. Use this skill when the user wants to check architecture, mentions "validate boundaries", "check imports", or needs dependency analysis.
description: This skill should be used when checking architecture compliance, validating layer boundaries (Feature→Feature violations), detecting circular dependencies, or user mentions "check architecture", "validate boundaries", "check imports". Validates import boundaries and architectural rules in ISA-Frontend monorepo.
---
# Architecture Enforcer

View File

@@ -1,6 +1,6 @@
---
name: circular-dependency-resolver
description: This skill should be used when detecting and resolving circular dependencies in the ISA-Frontend monorepo. It uses graph algorithms to find A→B→C→A cycles, categorizes by severity, provides multiple fix strategies (DI, interface extraction, shared code), and validates fixes. Use this skill when the user mentions "circular dependencies", "dependency cycles", or has build/runtime issues from circular imports.
description: This skill should be used when build fails with circular import warnings, user mentions "circular dependencies" or "dependency cycles", or fixing A→B→C→A import cycles. Detects and resolves circular dependencies using graph algorithms with DI, interface extraction, and shared code fix strategies.
---
# Circular Dependency Resolver

View File

@@ -0,0 +1,392 @@
---
name: css-keyframes-animations
description: This skill should be used when writing or reviewing CSS animations in Angular components. Use when creating entrance/exit animations, implementing @keyframes instead of @angular/animations, applying timing functions and fill modes, creating staggered animations, or ensuring GPU-accelerated performance. Essential for modern Angular 20+ components using animate.enter/animate.leave directives and converting legacy Angular animations to native CSS.
---
# CSS @keyframes Animations
## Overview
Implement native CSS @keyframes animations for Angular applications, replacing @angular/animations with GPU-accelerated, zero-bundle-size alternatives. This skill provides comprehensive guidance on creating performant entrance/exit animations, staggered effects, and proper timing configurations.
## When to Use This Skill
Apply this skill when:
- **Writing Angular components** with entrance/exit animations
- **Converting @angular/animations** to native CSS @keyframes
- **Implementing animate.enter/animate.leave** in Angular 20+ templates
- **Creating staggered animations** for lists or collections
- **Debugging animation issues** (snap-back, wrong starting positions, choppy playback)
- **Optimizing animation performance** for GPU acceleration
- **Reviewing animation code** for accessibility and best practices
## Quick Start
### Basic Animation Setup
1. **Define @keyframes** in component CSS:
```css
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
```
2. **Apply animation** to element:
```css
.element {
animation: fadeIn 0.3s ease-out;
}
```
3. **Use with Angular 20+ directives**:
```html
@if (visible()) {
<div animate.enter="fade-in" animate.leave="fade-out">
Content
</div>
}
```
### Common Pitfall: Element Snaps Back
**Problem:** Element returns to original state after animation completes.
**Solution:** Add `forwards` fill mode:
```css
.element {
animation: fadeOut 1s forwards;
}
```
### Common Pitfall: Animation Conflicts with State Transitions
**Problem:** Entrance animation overrides initial state transforms (e.g., stacked cards appear unstacked then jump).
**Solution:** Animate only properties that don't conflict with state. Use opacity-only animations when transforms are state-driven:
```css
/* BAD: Overrides stacked transform */
@keyframes cardEntrance {
from { transform: translateY(20px); opacity: 0; }
to { transform: translateY(0); opacity: 1; }
}
/* GOOD: Only animates opacity, allows state transforms to apply */
@keyframes cardEntrance {
from { opacity: 0; }
to { opacity: 1; }
}
```
## Core Principles
### 1. GPU-Accelerated Properties Only
**Always use** for animations:
- `transform` (translate, rotate, scale)
- `opacity`
**Avoid animating** (triggers layout recalculation):
- `width`, `height`
- `top`, `left`, `right`, `bottom`
- `margin`, `padding`
- `font-size`
### 2. Fill Modes
| Fill Mode | Behavior | Use Case |
|-----------|----------|----------|
| `forwards` | Keep end state | Exit animations (stay invisible) |
| `backwards` | Apply start state during delay | Entrance with delay (prevent flash) |
| `both` | Both of above | Complex sequences |
### 3. Timing Functions
Choose appropriate easing for animation type:
```css
/* Entrance animations - ease-out (fast start, slow end) */
animation-timing-function: cubic-bezier(0, 0, 0.58, 1);
/* Exit animations - ease-in (slow start, fast end) */
animation-timing-function: cubic-bezier(0.42, 0, 1, 1);
/* Bouncy overshoot effect */
animation-timing-function: cubic-bezier(0.34, 1.56, 0.64, 1);
```
Tool: [cubic-bezier.com](https://cubic-bezier.com) for custom curves.
### 4. Staggered Animations
Create cascading effects using CSS custom properties:
**Template:**
```html
@for (item of items(); track item.id; let idx = $index) {
<div [style.--i]="idx" class="stagger-item">
{{ item.name }}
</div>
}
```
**CSS:**
```css
.stagger-item {
animation: fadeSlideIn 0.5s ease-out backwards;
animation-delay: calc(var(--i, 0) * 100ms);
}
```
### 5. Accessibility
Always respect reduced motion preferences:
```css
@media (prefers-reduced-motion: reduce) {
.animated {
animation: none;
/* Or use simpler, faster animation */
animation-duration: 0.1s;
}
}
```
## Common Animation Patterns
### Fade Entrance/Exit
```css
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
.fade-in { animation: fadeIn 0.3s ease-out; }
.fade-out { animation: fadeOut 0.3s ease-in forwards; }
```
### Slide Entrance
```css
@keyframes slideInUp {
from {
opacity: 0;
transform: translateY(20px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
.slide-in-up { animation: slideInUp 0.3s ease-out; }
```
### Scale Entrance
```css
@keyframes scaleIn {
from {
opacity: 0;
transform: scale(0.9);
}
to {
opacity: 1;
transform: scale(1);
}
}
.scale-in { animation: scaleIn 0.2s ease-out; }
```
### Loading Spinner
```css
@keyframes spin {
to { transform: rotate(360deg); }
}
.spinner {
width: 40px;
height: 40px;
border: 3px solid #f3f3f3;
border-top: 3px solid #3498db;
border-radius: 50%;
animation: spin 1s linear infinite;
}
```
### Shake (Error Feedback)
```css
@keyframes shake {
0%, 100% { transform: translateX(0); }
10%, 30%, 50%, 70%, 90% { transform: translateX(-5px); }
20%, 40%, 60%, 80% { transform: translateX(5px); }
}
.error-input {
animation: shake 0.5s ease-in-out;
}
```
## Angular 20+ Integration
### Basic Usage with animate.enter/animate.leave
```typescript
@Component({
template: `
@if (show()) {
<div animate.enter="fade-in" animate.leave="fade-out">
Content
</div>
}
`,
styles: [`
.fade-in { animation: fadeIn 0.3s ease-out; }
.fade-out { animation: fadeOut 0.3s ease-in forwards; }
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
`]
})
```
### Dynamic Animation Classes
```typescript
@Component({
template: `
@if (show()) {
<div [animate.enter]="enterAnim()" [animate.leave]="leaveAnim()">
Content
</div>
}
`
})
export class DynamicAnimComponent {
show = signal(false);
enterAnim = signal('slide-in-up');
leaveAnim = signal('slide-out-down');
}
```
## Debugging Animations
### Common Issues
| Problem | Cause | Solution |
|---------|-------|----------|
| Animation doesn't run | Missing duration | Add `animation-duration: 0.3s` |
| Element snaps back | No fill mode | Add `animation-fill-mode: forwards` |
| Wrong starting position during delay | No backwards fill | Add `animation-fill-mode: backwards` |
| Choppy animation | Animating layout properties | Use `transform` instead |
| State conflict (jump/snap) | Animation overrides state transforms | Animate only opacity, not transform |
### Browser DevTools
- **Chrome DevTools** → More Tools → Animations panel
- **Firefox DevTools** → Inspector → Animations tab
### Animation Events
```typescript
element.addEventListener('animationend', (e) => {
console.log('Animation completed:', e.animationName);
// Clean up, remove element, etc.
});
```
## Resources
### references/keyframes-guide.md
Comprehensive deep-dive covering:
- Complete @keyframes syntax reference
- Detailed timing functions and cubic-bezier curves
- Advanced techniques (direction, play-state, @starting-style)
- Performance optimization strategies
- Extensive common patterns library
- Debugging techniques and troubleshooting
**When to reference:** Complex animation requirements, custom easing curves, advanced techniques, performance optimization, or learning comprehensive details.
### assets/animations.css
Ready-to-use CSS file with common animation patterns:
- Fade animations (in/out)
- Slide animations (up/down/left/right)
- Scale animations (in/out)
- Utility animations (spin, shimmer, shake, breathe, attention-pulse)
- Toast/notification animations
- Accessibility (@media prefers-reduced-motion)
**Usage:** Copy this file to project and import in component styles or global styles:
```css
@import 'path/to/animations.css';
```
Then use classes directly:
```html
<div animate.enter="fade-in" animate.leave="slide-out-down">
```
## Migration from @angular/animations
### Before (Angular Animations)
```typescript
import { trigger, state, style, transition, animate } from '@angular/animations';
@Component({
animations: [
trigger('fadeIn', [
transition(':enter', [
style({ opacity: 0 }),
animate('300ms ease-out', style({ opacity: 1 }))
])
])
]
})
```
### After (CSS @keyframes)
```typescript
@Component({
template: `
@if (show()) {
<div animate.enter="fade-in">Content</div>
}
`,
styles: [`
.fade-in { animation: fadeIn 0.3s ease-out; }
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
`]
})
```
**Benefits:**
- Zero JavaScript bundle size (~60KB savings)
- GPU hardware acceleration
- Standard CSS (transferable skills)
- Better performance

View File

@@ -0,0 +1,278 @@
/**
* Reusable CSS @keyframes Animations
*
* Common animation patterns for Angular applications.
* Import this file in your component styles or global styles.
*/
/* ============================================
FADE ANIMATIONS
============================================ */
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
.fade-in {
animation: fadeIn 0.3s ease-out;
}
.fade-out {
animation: fadeOut 0.3s ease-in;
}
/* ============================================
SLIDE ANIMATIONS
============================================ */
@keyframes slideInUp {
from {
opacity: 0;
transform: translateY(20px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
@keyframes slideOutDown {
from {
opacity: 1;
transform: translateY(0);
}
to {
opacity: 0;
transform: translateY(20px);
}
}
@keyframes slideInDown {
from {
opacity: 0;
transform: translateY(-20px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
@keyframes slideOutUp {
from {
opacity: 1;
transform: translateY(0);
}
to {
opacity: 0;
transform: translateY(-20px);
}
}
@keyframes slideInLeft {
from {
opacity: 0;
transform: translateX(-20px);
}
to {
opacity: 1;
transform: translateX(0);
}
}
@keyframes slideOutLeft {
from {
opacity: 1;
transform: translateX(0);
}
to {
opacity: 0;
transform: translateX(-20px);
}
}
@keyframes slideInRight {
from {
opacity: 0;
transform: translateX(20px);
}
to {
opacity: 1;
transform: translateX(0);
}
}
@keyframes slideOutRight {
from {
opacity: 1;
transform: translateX(0);
}
to {
opacity: 0;
transform: translateX(20px);
}
}
.slide-in-up { animation: slideInUp 0.3s ease-out; }
.slide-out-down { animation: slideOutDown 0.3s ease-in; }
.slide-in-down { animation: slideInDown 0.3s ease-out; }
.slide-out-up { animation: slideOutUp 0.3s ease-in; }
.slide-in-left { animation: slideInLeft 0.3s ease-out; }
.slide-out-left { animation: slideOutLeft 0.3s ease-in; }
.slide-in-right { animation: slideInRight 0.3s ease-out; }
.slide-out-right { animation: slideOutRight 0.3s ease-in; }
/* ============================================
SCALE ANIMATIONS
============================================ */
@keyframes scaleIn {
from {
opacity: 0;
transform: scale(0.9);
}
to {
opacity: 1;
transform: scale(1);
}
}
@keyframes scaleOut {
from {
opacity: 1;
transform: scale(1);
}
to {
opacity: 0;
transform: scale(0.9);
}
}
.scale-in { animation: scaleIn 0.2s ease-out; }
.scale-out { animation: scaleOut 0.2s ease-in; }
/* ============================================
UTILITY ANIMATIONS
============================================ */
/* Loading Spinner */
@keyframes spin {
to { transform: rotate(360deg); }
}
.spin {
animation: spin 1s linear infinite;
}
/* Skeleton Loading */
@keyframes shimmer {
0% { background-position: -200% 0; }
100% { background-position: 200% 0; }
}
.shimmer {
background: linear-gradient(
90deg,
#f0f0f0 25%,
#e0e0e0 50%,
#f0f0f0 75%
);
background-size: 200% 100%;
animation: shimmer 1.5s infinite;
}
/* Attention Pulse */
@keyframes attention-pulse {
0%, 100% {
box-shadow: 0 0 0 0 rgba(59, 130, 246, 0.5);
}
50% {
box-shadow: 0 0 0 10px rgba(59, 130, 246, 0);
}
}
.attention-pulse {
animation: attention-pulse 2s ease-in-out infinite;
}
/* Shake (Error Feedback) */
@keyframes shake {
0%, 100% { transform: translateX(0); }
10%, 30%, 50%, 70%, 90% { transform: translateX(-5px); }
20%, 40%, 60%, 80% { transform: translateX(5px); }
}
.shake {
animation: shake 0.5s ease-in-out;
}
/* Breathing/Pulsing */
@keyframes breathe {
0%, 100% {
opacity: 1;
transform: scale(1);
}
50% {
opacity: 0.7;
transform: scale(1.05);
}
}
.breathe {
animation: breathe 2s ease-in-out infinite;
}
/* ============================================
TOAST/NOTIFICATION ANIMATIONS
============================================ */
@keyframes toastIn {
from {
opacity: 0;
transform: translateY(100%) scale(0.9);
}
to {
opacity: 1;
transform: translateY(0) scale(1);
}
}
@keyframes toastOut {
from {
opacity: 1;
transform: translateY(0) scale(1);
}
to {
opacity: 0;
transform: translateY(100%) scale(0.9);
}
}
.toast-in {
animation: toastIn 0.3s cubic-bezier(0.34, 1.56, 0.64, 1);
}
.toast-out {
animation: toastOut 0.2s ease-in forwards;
}
/* ============================================
ACCESSIBILITY
============================================ */
/* Respect user's motion preferences */
@media (prefers-reduced-motion: reduce) {
*,
*::before,
*::after {
animation-duration: 0.01ms !important;
animation-iteration-count: 1 !important;
transition-duration: 0.01ms !important;
}
}

View File

@@ -0,0 +1,833 @@
# CSS @keyframes Deep Dive
A comprehensive guide for Angular developers transitioning from `@angular/animations` to native CSS animations.
---
## Table of Contents
1. [Understanding @keyframes](#understanding-keyframes)
2. [Basic Syntax](#basic-syntax)
3. [Animation Properties](#animation-properties)
4. [Timing Functions (Easing)](#timing-functions-easing)
5. [Fill Modes](#fill-modes)
6. [Advanced Techniques](#advanced-techniques)
7. [Angular 20+ Integration](#angular-20-integration)
8. [Common Patterns & Recipes](#common-patterns--recipes)
9. [Performance Tips](#performance-tips)
10. [Debugging Animations](#debugging-animations)
---
## Understanding @keyframes
The `@keyframes` at-rule controls the intermediate steps in a CSS animation sequence by defining styles for keyframes (waypoints) along the animation. Unlike transitions (which only animate between two states), keyframes let you define multiple intermediate steps.
### How It Differs from @angular/animations
| @angular/animations | Native CSS @keyframes |
|---------------------|----------------------|
| ~60KB JavaScript bundle | Zero JS overhead |
| CPU-based rendering | GPU hardware acceleration |
| Angular-specific syntax | Standard CSS (transferable skills) |
| `trigger()`, `state()`, `animate()` | `@keyframes` + CSS classes |
---
## Basic Syntax
### The @keyframes Rule
```css
@keyframes animation-name {
from {
/* Starting styles (same as 0%) */
}
to {
/* Ending styles (same as 100%) */
}
}
```
### Percentage-Based Keyframes
For more control, use percentages to define multiple waypoints:
```css
@keyframes bounce {
0% {
transform: translateY(0);
}
25% {
transform: translateY(-30px);
}
50% {
transform: translateY(0);
}
75% {
transform: translateY(-15px);
}
100% {
transform: translateY(0);
}
}
```
### Combining Multiple Percentages
You can apply the same styles to multiple keyframes:
```css
@keyframes pulse {
0%, 100% {
opacity: 1;
transform: scale(1);
}
50% {
opacity: 0.7;
transform: scale(1.05);
}
}
```
### Applying the Animation
```css
.element {
animation: bounce 1s ease-in-out infinite;
}
```
---
## Animation Properties
### Individual Properties
| Property | Description | Example |
|----------|-------------|---------|
| `animation-name` | Name of the @keyframes | `animation-name: bounce;` |
| `animation-duration` | How long one cycle takes | `animation-duration: 2s;` |
| `animation-timing-function` | Speed curve (easing) | `animation-timing-function: ease-in;` |
| `animation-delay` | Wait before starting | `animation-delay: 500ms;` |
| `animation-iteration-count` | How many times to run | `animation-iteration-count: 3;` or `infinite` |
| `animation-direction` | Forward, reverse, or alternate | `animation-direction: alternate;` |
| `animation-fill-mode` | Styles before/after animation | `animation-fill-mode: forwards;` |
| `animation-play-state` | Pause or play | `animation-play-state: paused;` |
### Shorthand Syntax
```css
/* animation: name duration timing-function delay iteration-count direction fill-mode play-state */
.element {
animation: slideIn 0.5s ease-out 0.2s 1 normal forwards running;
}
```
**Minimum required:** name and duration
```css
.element {
animation: fadeIn 1s;
}
```
### Multiple Animations
Apply multiple animations to a single element:
```css
.element {
animation:
fadeIn 0.5s ease-out,
slideUp 0.5s ease-out,
pulse 2s ease-in-out 0.5s infinite;
}
```
---
## Timing Functions (Easing)
The timing function controls how the animation progresses over time—where it speeds up and slows down.
### Keyword Values
| Keyword | Cubic-Bezier Equivalent | Description |
|---------|------------------------|-------------|
| `linear` | `cubic-bezier(0, 0, 1, 1)` | Constant speed |
| `ease` | `cubic-bezier(0.25, 0.1, 0.25, 1)` | Default: slow start, fast middle, slow end |
| `ease-in` | `cubic-bezier(0.42, 0, 1, 1)` | Slow start, fast end |
| `ease-out` | `cubic-bezier(0, 0, 0.58, 1)` | Fast start, slow end |
| `ease-in-out` | `cubic-bezier(0.42, 0, 0.58, 1)` | Slow start and end |
### Custom Cubic-Bezier
Create custom easing curves with `cubic-bezier(x1, y1, x2, y2)`:
```css
/* Bouncy overshoot effect */
.element {
animation-timing-function: cubic-bezier(0.68, -0.6, 0.32, 1.6);
}
/* Smooth deceleration */
.element {
animation-timing-function: cubic-bezier(0.25, 1, 0.5, 1);
}
```
**Tool:** Use [cubic-bezier.com](https://cubic-bezier.com) to visualize and create custom curves.
### Popular Easing Functions
```css
/* Ease Out Quart - Great for enter animations */
cubic-bezier(0.25, 1, 0.5, 1)
/* Ease In Out Cubic - Smooth state changes */
cubic-bezier(0.65, 0, 0.35, 1)
/* Ease Out Back - Slight overshoot */
cubic-bezier(0.34, 1.56, 0.64, 1)
/* Ease In Out Back - Overshoot both ends */
cubic-bezier(0.68, -0.6, 0.32, 1.6)
```
### Steps Function
For frame-by-frame animations (like sprite sheets):
```css
/* 6 discrete steps */
.sprite {
animation: walk 1s steps(6) infinite;
}
/* Step positions */
steps(4, jump-start) /* Jump at start of each interval */
steps(4, jump-end) /* Jump at end of each interval (default) */
steps(4, jump-both) /* Jump at both ends */
steps(4, jump-none) /* No jump at ends */
```
### Timing Function Per Keyframe
Apply different easing to different segments:
```css
@keyframes complexMove {
0% {
transform: translateX(0);
animation-timing-function: ease-out;
}
50% {
transform: translateX(100px);
animation-timing-function: ease-in;
}
100% {
transform: translateX(200px);
}
}
```
**Important:** The timing function applies to each step individually, not the entire animation.
---
## Fill Modes
Fill modes control what styles apply before and after the animation runs.
### Values
| Value | Before Animation | After Animation |
|-------|-----------------|-----------------|
| `none` | Original styles | Original styles |
| `forwards` | Original styles | **Last keyframe styles** |
| `backwards` | **First keyframe styles** | Original styles |
| `both` | **First keyframe styles** | **Last keyframe styles** |
### Common Problem: Element Snaps Back
```css
/* BAD: Element disappears then reappears after animation */
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
.element {
animation: fadeOut 1s; /* Element snaps back to opacity: 1 */
}
/* GOOD: Element stays invisible */
.element {
animation: fadeOut 1s forwards;
}
```
### Backwards Fill Mode (for delays)
```css
@keyframes slideIn {
from {
transform: translateX(-100%);
opacity: 0;
}
to {
transform: translateX(0);
opacity: 1;
}
}
/* Without backwards: element visible at original position during delay */
/* With backwards: element starts at first keyframe position during delay */
.element {
animation: slideIn 0.5s ease-out 1s backwards;
}
```
---
## Advanced Techniques
### Animation Direction
Control playback direction:
```css
animation-direction: normal; /* 0% → 100% */
animation-direction: reverse; /* 100% → 0% */
animation-direction: alternate; /* 0% → 100% → 0% */
animation-direction: alternate-reverse; /* 100% → 0% → 100% */
```
**Use Case:** Breathing/pulsing effects
```css
@keyframes breathe {
from { transform: scale(1); }
to { transform: scale(1.1); }
}
.element {
animation: breathe 2s ease-in-out infinite alternate;
}
```
### Staggered Animations
Create cascading effects with animation-delay:
```css
.item { animation: fadeSlideIn 0.5s ease-out backwards; }
.item:nth-child(1) { animation-delay: 0ms; }
.item:nth-child(2) { animation-delay: 100ms; }
.item:nth-child(3) { animation-delay: 200ms; }
.item:nth-child(4) { animation-delay: 300ms; }
/* Or use CSS custom properties */
.item {
animation: fadeSlideIn 0.5s ease-out backwards;
animation-delay: calc(var(--i, 0) * 100ms);
}
```
In your template:
```html
<div class="item" style="--i: 0">First</div>
<div class="item" style="--i: 1">Second</div>
<div class="item" style="--i: 2">Third</div>
```
### @starting-style (Modern CSS)
Define styles for when an element first enters the DOM:
```css
.modal {
opacity: 1;
transform: scale(1);
transition: opacity 0.3s, transform 0.3s;
@starting-style {
opacity: 0;
transform: scale(0.9);
}
}
```
### Animating Auto Height
Use CSS Grid for height: auto animations:
```css
.accordion-content {
display: grid;
grid-template-rows: 0fr;
transition: grid-template-rows 0.3s ease-out;
}
.accordion-content.open {
grid-template-rows: 1fr;
}
.accordion-content > div {
overflow: hidden;
}
```
### Pause/Play with CSS
```css
.element {
animation: spin 2s linear infinite;
animation-play-state: running;
}
.element:hover {
animation-play-state: paused;
}
/* Or with a class */
.element.paused {
animation-play-state: paused;
}
```
---
## Angular 20+ Integration
### Using animate.enter and animate.leave
Angular 20.2+ provides `animate.enter` and `animate.leave` to apply CSS classes when elements enter/leave the DOM.
```typescript
@Component({
selector: 'app-example',
template: `
@if (isVisible()) {
<div animate.enter="fade-in" animate.leave="fade-out">
Content here
</div>
}
<button (click)="toggle()">Toggle</button>
`,
styles: [`
.fade-in {
animation: fadeIn 0.3s ease-out;
}
.fade-out {
animation: fadeOut 0.3s ease-in;
}
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
`]
})
export class ExampleComponent {
isVisible = signal(false);
toggle() { this.isVisible.update(v => !v); }
}
```
### Dynamic Animation Classes
```typescript
@Component({
template: `
@if (show()) {
<div [animate.enter]="enterAnimation()" [animate.leave]="leaveAnimation()">
Dynamic animations!
</div>
}
`
})
export class DynamicAnimComponent {
show = signal(false);
enterAnimation = signal('slide-in-right');
leaveAnimation = signal('slide-out-left');
}
```
### Reusable Animation CSS File
Create a shared `animations.css`:
```css
/* animations.css */
/* Fade animations */
.fade-in { animation: fadeIn 0.3s ease-out; }
.fade-out { animation: fadeOut 0.3s ease-in; }
@keyframes fadeIn {
from { opacity: 0; }
to { opacity: 1; }
}
@keyframes fadeOut {
from { opacity: 1; }
to { opacity: 0; }
}
/* Slide animations */
.slide-in-up { animation: slideInUp 0.3s ease-out; }
.slide-out-down { animation: slideOutDown 0.3s ease-in; }
@keyframes slideInUp {
from {
opacity: 0;
transform: translateY(20px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
@keyframes slideOutDown {
from {
opacity: 1;
transform: translateY(0);
}
to {
opacity: 0;
transform: translateY(20px);
}
}
/* Scale animations */
.scale-in { animation: scaleIn 0.2s ease-out; }
.scale-out { animation: scaleOut 0.2s ease-in; }
@keyframes scaleIn {
from {
opacity: 0;
transform: scale(0.9);
}
to {
opacity: 1;
transform: scale(1);
}
}
@keyframes scaleOut {
from {
opacity: 1;
transform: scale(1);
}
to {
opacity: 0;
transform: scale(0.9);
}
}
```
Import in `styles.css` or `angular.json`:
```css
@import 'animations.css';
```
---
## Common Patterns & Recipes
### Loading Spinner
```css
@keyframes spin {
to { transform: rotate(360deg); }
}
.spinner {
width: 40px;
height: 40px;
border: 3px solid #f3f3f3;
border-top: 3px solid #3498db;
border-radius: 50%;
animation: spin 1s linear infinite;
}
```
### Skeleton Loading
```css
@keyframes shimmer {
0% { background-position: -200% 0; }
100% { background-position: 200% 0; }
}
.skeleton {
background: linear-gradient(
90deg,
#f0f0f0 25%,
#e0e0e0 50%,
#f0f0f0 75%
);
background-size: 200% 100%;
animation: shimmer 1.5s infinite;
}
```
### Attention Pulse
```css
@keyframes attention-pulse {
0%, 100% {
box-shadow: 0 0 0 0 rgba(59, 130, 246, 0.5);
}
50% {
box-shadow: 0 0 0 10px rgba(59, 130, 246, 0);
}
}
.notification-badge {
animation: attention-pulse 2s ease-in-out infinite;
}
```
### Shake (Error Feedback)
```css
@keyframes shake {
0%, 100% { transform: translateX(0); }
10%, 30%, 50%, 70%, 90% { transform: translateX(-5px); }
20%, 40%, 60%, 80% { transform: translateX(5px); }
}
.error-input {
animation: shake 0.5s ease-in-out;
}
```
### Slide Down Menu
```css
@keyframes slideDown {
from {
opacity: 0;
transform: translateY(-10px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
.dropdown-menu {
animation: slideDown 0.2s ease-out forwards;
}
```
### Toast Notification
```css
@keyframes toastIn {
from {
opacity: 0;
transform: translateY(100%) scale(0.9);
}
to {
opacity: 1;
transform: translateY(0) scale(1);
}
}
@keyframes toastOut {
from {
opacity: 1;
transform: translateY(0) scale(1);
}
to {
opacity: 0;
transform: translateY(100%) scale(0.9);
}
}
.toast {
animation: toastIn 0.3s cubic-bezier(0.34, 1.56, 0.64, 1);
}
.toast.leaving {
animation: toastOut 0.2s ease-in forwards;
}
```
---
## Performance Tips
### Use Transform and Opacity
These properties are GPU-accelerated and don't trigger layout:
```css
/* GOOD - GPU accelerated */
@keyframes good {
from { transform: translateX(0); opacity: 0; }
to { transform: translateX(100px); opacity: 1; }
}
/* AVOID - Triggers layout recalculation */
@keyframes avoid {
from { left: 0; width: 100px; }
to { left: 100px; width: 200px; }
}
```
### Use will-change Sparingly
```css
.element {
will-change: transform, opacity;
}
/* Remove after animation */
.element.animation-complete {
will-change: auto;
}
```
### Respect Reduced Motion
```css
@keyframes fadeSlide {
from {
opacity: 0;
transform: translateY(20px);
}
to {
opacity: 1;
transform: translateY(0);
}
}
.element {
animation: fadeSlide 0.3s ease-out;
}
@media (prefers-reduced-motion: reduce) {
.element {
animation: none;
/* Or use a simpler fade */
animation: fadeIn 0.1s ease-out;
}
}
```
### Avoid Animating Layout Properties
Properties that trigger layout (reflow):
- `width`, `height`
- `top`, `left`, `right`, `bottom`
- `margin`, `padding`
- `font-size`
- `border-width`
Use `transform: scale()` instead of `width/height` when possible.
---
## Debugging Animations
### Browser DevTools
1. **Chrome DevTools** → More Tools → Animations
- Pause, slow down, or step through animations
- Inspect timing curves
2. **Firefox** → Inspector → Animations tab
- Visual timeline of all animations
### Force Slow Motion
```css
/* Temporarily add to debug */
* {
animation-duration: 3s !important;
}
```
### Animation Events in JavaScript
```typescript
element.addEventListener('animationstart', (e) => {
console.log('Started:', e.animationName);
});
element.addEventListener('animationend', (e) => {
console.log('Ended:', e.animationName);
// Clean up class, remove element, etc.
});
element.addEventListener('animationiteration', (e) => {
console.log('Iteration:', e.animationName);
});
```
### Common Issues
| Problem | Solution |
|---------|----------|
| Animation not running | Check `animation-duration` is > 0 |
| Element snaps back | Add `animation-fill-mode: forwards` |
| Animation starts wrong | Use `animation-fill-mode: backwards` with delay |
| Choppy animation | Use `transform` instead of layout properties |
| Animation restarts on state change | Ensure Angular doesn't recreate the element |
---
## Quick Reference Card
```css
/* Basic setup */
@keyframes name {
from { /* start */ }
to { /* end */ }
}
.element {
animation: name 0.3s ease-out forwards;
}
/* Angular 20+ */
<div animate.enter="fade-in" animate.leave="fade-out">
/* Shorthand order */
animation: name duration timing delay count direction fill-mode state;
/* Common timing functions */
ease-out: cubic-bezier(0, 0, 0.58, 1) /* Enter animations */
ease-in: cubic-bezier(0.42, 0, 1, 1) /* Exit animations */
ease-in-out: cubic-bezier(0.42, 0, 0.58, 1) /* State changes */
/* Fill modes */
forwards Keep end state
backwards Apply start state during delay
both Both of the above
```
---
## Resources
- [MDN CSS Animations Guide](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_animations/Using_CSS_animations)
- [Angular Animation Migration Guide](https://angular.dev/guide/animations/migration)
- [Cubic Bezier Tool](https://cubic-bezier.com)
- [Easing Functions Cheat Sheet](https://easings.net)
- [Josh W. Comeau's Keyframe Guide](https://www.joshwcomeau.com/animation/keyframe-animations/)

View File

@@ -0,0 +1,352 @@
---
name: git-workflow
description: This skill should be used when creating branches, writing commits, or creating pull requests. Enforces ISA-Frontend Git conventions including feature/task-id-name branch format, conventional commits without co-author tags, and PRs targeting develop branch.
---
# Git Workflow Skill
Enforces Git workflow conventions specific to the ISA-Frontend project.
## When to Use
- Creating new branches for features or bugfixes
- Writing commit messages
- Creating pull requests
- Any Git operations requiring adherence to project conventions
## Core Principles
### 1. Default Branch is `develop` (NOT `main`)
- **All PRs target**: `develop` branch
- **Feature branches from**: `develop`
- **Never push directly to**: `develop` or `main`
### 2. Branch Naming Convention
**Format**: `<type>/{task-id}-{short-description}`
**Types**:
- `feature/` - New features or enhancements
- `bugfix/` - Bug fixes
- `hotfix/` - Emergency production fixes
**Rules**:
- Use English kebab-case for descriptions
- Start with task/issue ID (e.g., `5391`)
- Keep description concise - shorten if too long
- Use hyphens to separate words
**Examples**:
```bash
# Good
feature/5391-praemie-checkout-action-card-delivery-order
bugfix/6123-fix-login-redirect-loop
hotfix/7890-critical-payment-error
# Bad
feature/praemie-checkout # Missing task ID
feature/5391_praemie # Using underscores
feature-5391-very-long-description-that-goes-on-forever # Too long
```
### 3. Conventional Commits (WITHOUT Co-Author Tags)
**Format**: `<type>(<scope>): <description>`
**Types**:
- `feat`: New feature
- `fix`: Bug fix
- `docs`: Documentation only
- `style`: Code style (formatting, missing semicolons)
- `refactor`: Code restructuring without feature changes
- `perf`: Performance improvements
- `test`: Adding or updating tests
- `build`: Build system or dependencies
- `ci`: CI configuration
- `chore`: Maintenance tasks
**Rules**:
-**NO** "Generated with Claude Code" tags
-**NO** "Co-Authored-By: Claude" tags
- ✅ Keep first line under 72 characters
- ✅ Use imperative mood ("add" not "added")
- ✅ Body optional but recommended for complex changes
**Examples**:
```bash
# Good
feat(checkout): add bonus card selection for delivery orders
fix(crm): resolve customer search filter reset issue
refactor(oms): extract return validation logic into service
# Bad
feat(checkout): add bonus card selection
Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
# Also bad
Added new feature # Wrong tense
Fix bug # Missing scope
```
### 4. Pull Request Creation
**Target Branch**: Always `develop`
**PR Title Format**: Same as conventional commit
```
feat(domain): concise description of changes
```
**PR Body Structure**:
```markdown
## Summary
- Brief bullet points of changes
## Related Tasks
- Closes #{task-id}
- Refs #{related-task}
## Test Plan
- [ ] Unit tests added/updated
- [ ] E2E attributes added
- [ ] Manual testing completed
## Breaking Changes
None / List breaking changes
## Screenshots (if UI changes)
[Add screenshots]
```
## Common Workflows
### Creating a Feature Branch
```bash
# 1. Update develop
git checkout develop
git pull origin develop
# 2. Create feature branch
git checkout -b feature/5391-praemie-checkout-action-card
# 3. Work and commit
git add .
git commit -m "feat(checkout): add primary bonus card selection logic"
# 4. Push to remote
git push -u origin feature/5391-praemie-checkout-action-card
# 5. Create PR targeting develop (use gh CLI or web UI)
```
### Creating a Bugfix Branch
```bash
# From develop
git checkout develop
git pull origin develop
git checkout -b bugfix/6123-login-redirect-loop
# Commit
git commit -m "fix(auth): resolve infinite redirect on logout"
```
### Creating a Hotfix Branch
```bash
# From main (production)
git checkout main
git pull origin main
git checkout -b hotfix/7890-payment-processing-error
# Commit
git commit -m "fix(checkout): critical payment API timeout handling"
# Merge to both main and develop
```
## Commit Message Guidelines
### Good Commit Messages
```bash
feat(crm): add customer loyalty tier calculation
Implements three-tier loyalty system based on annual spend.
Includes migration for existing customer data.
Refs #5234
---
fix(oms): prevent duplicate return submissions
Adds debouncing to return form submission and validates
against existing returns in the last 60 seconds.
Closes #5891
---
refactor(catalogue): extract product search into dedicated service
Moves search logic from component to ProductSearchService
for better testability and reusability.
---
perf(remission): optimize remission list query with pagination
Reduces initial load time from 3s to 800ms by implementing
cursor-based pagination.
Closes #6234
```
### Bad Commit Messages
```bash
# Too vague
fix: bug fixes
# Missing scope
feat: new feature
# Wrong tense
fixed the login issue
# Including banned tags
feat(checkout): add feature
Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
```
## Git Configuration Checks
### Verify Git Setup
```bash
# Check current branch
git branch --show-current
# Verify remote
git remote -v # Should show origin pointing to ISA-Frontend
# Check for uncommitted changes
git status
```
## Common Mistakes to Avoid
```bash
# ❌ Creating PR against main
gh pr create --base main # WRONG
# ✅ Always target develop
gh pr create --base develop # CORRECT
# ❌ Using underscores in branch names
git checkout -b feature/5391_my_feature # WRONG
# ✅ Use hyphens
git checkout -b feature/5391-my-feature # CORRECT
# ❌ Adding co-author tags
git commit -m "feat: something
Co-Authored-By: Claude <noreply@anthropic.com>" # WRONG
# ✅ Clean commit message
git commit -m "feat(scope): something" # CORRECT
# ❌ Forgetting task ID in branch name
git checkout -b feature/new-checkout-flow # WRONG
# ✅ Include task ID
git checkout -b feature/5391-new-checkout-flow # CORRECT
```
## Integration with Claude Code
When Claude Code creates commits or PRs:
### Commit Creation
```bash
# Claude uses conventional commits WITHOUT attribution
git commit -m "feat(checkout): implement bonus card selection
Adds logic for selecting primary bonus card during checkout
for delivery orders. Includes validation and error handling.
Refs #5391"
```
### PR Creation
```bash
# Target develop by default
gh pr create --base develop \
--title "feat(checkout): implement bonus card selection" \
--body "## Summary
- Add primary bonus card selection logic
- Implement validation for delivery orders
- Add error handling for API failures
## Related Tasks
- Closes #5391
## Test Plan
- [x] Unit tests added
- [x] E2E attributes added
- [x] Manual testing completed"
```
## Branch Cleanup
### After PR Merge
```bash
# Update develop
git checkout develop
git pull origin develop
# Delete local feature branch
git branch -d feature/5391-praemie-checkout
# Delete remote branch (usually done by PR merge)
git push origin --delete feature/5391-praemie-checkout
```
## Quick Reference
```bash
# Branch naming
feature/{task-id}-{description}
bugfix/{task-id}-{description}
hotfix/{task-id}-{description}
# Commit format
<type>(<scope>): <description>
# Common types
feat, fix, docs, style, refactor, perf, test, build, ci, chore
# PR target
Always: develop (NOT main)
# Banned in commits
- "Generated with Claude Code"
- "Co-Authored-By: Claude"
- Any AI attribution
```
## Resources
- [Conventional Commits](https://www.conventionalcommits.org/)
- Project PR template: `.github/pull_request_template.md`
- Code review standards: `.github/review-instructions.md`

View File

@@ -0,0 +1,299 @@
---
name: html-template
description: This skill should be used when writing or reviewing HTML templates to ensure proper E2E testing attributes (data-what, data-which) and ARIA accessibility attributes are included. Use when creating interactive elements like buttons, inputs, links, forms, dialogs, or any HTML markup requiring testing and accessibility compliance. Works seamlessly with the angular-template skill.
---
# HTML Template - Testing & Accessibility Attributes
This skill should be used when writing or reviewing HTML templates to ensure proper testing and accessibility attributes are included.
## When to Use This Skill
Use this skill when:
- Writing or modifying Angular component templates
- Creating any HTML templates or markup
- Reviewing code for testing and accessibility compliance
- Adding interactive elements (buttons, inputs, links, etc.)
- Implementing forms, lists, navigation, or dialogs
**Works seamlessly with:**
- **[angular-template](../angular-template/SKILL.md)** - Angular template syntax, control flow, and modern patterns
- **[tailwind](../tailwind/SKILL.md)** - ISA design system styling for visual design
- **[logging](../logging/SKILL.md)** - MANDATORY logging in all Angular components using `@isa/core/logging`
## Overview
This skill provides comprehensive guidance for two critical HTML attribute categories:
### 1. E2E Testing Attributes
Enable automated end-to-end testing by providing stable selectors for QA automation:
- **`data-what`**: Semantic description of element's purpose
- **`data-which`**: Unique identifier for specific instances
- **`data-*`**: Additional contextual information
### 2. ARIA Accessibility Attributes
Ensure web applications are accessible to all users, including those using assistive technologies:
- **Roles**: Define element purpose (button, navigation, dialog, etc.)
- **Properties**: Provide additional context (aria-label, aria-describedby)
- **States**: Indicate dynamic states (aria-expanded, aria-disabled)
- **Live Regions**: Announce dynamic content changes
## Why Both Are Essential
- **E2E Attributes**: Enable reliable automated testing without brittle CSS or XPath selectors
- **ARIA Attributes**: Ensure compliance with WCAG standards and improve user experience for people with disabilities
- **Together**: Create robust, testable, and accessible web applications
## Quick Reference
### Button Example
```html
<button
type="button"
(click)="onSubmit()"
data-what="submit-button"
data-which="registration-form"
aria-label="Submit registration form">
Submit
</button>
```
### Input Example
```html
<input
type="text"
[(ngModel)]="email"
data-what="email-input"
data-which="registration-form"
aria-label="Email address"
aria-describedby="email-hint"
aria-required="true" />
<span id="email-hint">We'll never share your email</span>
```
### Dynamic List Example
```html
@for (item of items; track item.id) {
<li
(click)="selectItem(item)"
data-what="list-item"
[attr.data-which]="item.id"
[attr.data-status]="item.status"
[attr.aria-label]="'Select ' + item.name"
role="button"
tabindex="0">
{{ item.name }}
</li>
}
```
### Link Example
```html
<a
[routerLink]="['/orders', orderId]"
data-what="order-link"
[attr.data-which]="orderId"
[attr.aria-label]="'View order ' + orderNumber">
View Order #{{ orderNumber }}
</a>
```
### Dialog Example
```html
<div
class="dialog"
data-what="confirmation-dialog"
data-which="delete-item"
role="dialog"
aria-modal="true"
aria-labelledby="dialog-title"
aria-describedby="dialog-description">
<h2 id="dialog-title">Confirm Deletion</h2>
<p id="dialog-description">Are you sure you want to delete this item?</p>
<button
(click)="confirm()"
data-what="confirm-button"
data-which="delete-dialog"
aria-label="Confirm deletion">
Delete
</button>
<button
(click)="cancel()"
data-what="cancel-button"
data-which="delete-dialog"
aria-label="Cancel deletion">
Cancel
</button>
</div>
```
## Common Patterns by Element Type
### Interactive Elements That Need Attributes
**Required attributes for:**
- Buttons (`<button>`, `<ui-button>`, custom button components)
- Form inputs (`<input>`, `<textarea>`, `<select>`)
- Links (`<a>`, `[routerLink]`)
- Clickable elements (elements with `(click)` handlers)
- Custom interactive components
- List items in dynamic lists
- Navigation items
- Dialog/modal controls
### Naming Conventions
**E2E `data-what` patterns:**
- `*-button` (submit-button, cancel-button, delete-button)
- `*-input` (email-input, search-input, quantity-input)
- `*-link` (product-link, order-link, customer-link)
- `*-item` (list-item, menu-item, card-item)
- `*-dialog` (confirm-dialog, error-dialog, info-dialog)
- `*-dropdown` (status-dropdown, category-dropdown)
**E2E `data-which` guidelines:**
- Use unique identifiers: `data-which="primary"`, `data-which="customer-list"`
- Bind dynamically for lists: `[attr.data-which]="item.id"`
- Combine with context: `data-which="customer-{{ customerId }}-edit"`
**ARIA role patterns:**
- Interactive elements: `button`, `link`, `menuitem`
- Structural: `navigation`, `main`, `complementary`, `contentinfo`
- Widget: `dialog`, `alertdialog`, `tooltip`, `tablist`, `tab`
- Landmark: `banner`, `search`, `form`, `region`
## Best Practices
### E2E Attributes
1. ✅ Add to ALL interactive elements
2. ✅ Use kebab-case for `data-what` values
3. ✅ Ensure `data-which` is unique within the view
4. ✅ Use Angular binding for dynamic values: `[attr.data-*]`
5. ✅ Avoid including sensitive data in attributes
6. ✅ Document complex attribute patterns in template comments
### ARIA Attributes
1. ✅ Use semantic HTML first (use `<button>` instead of `<div role="button">`)
2. ✅ Provide text alternatives for all interactive elements
3. ✅ Ensure proper keyboard navigation (tabindex, focus management)
4. ✅ Use `aria-label` when visual label is missing
5. ✅ Use `aria-labelledby` to reference existing visible labels
6. ✅ Keep ARIA attributes in sync with visual states
7. ✅ Test with screen readers (NVDA, JAWS, VoiceOver)
### Combined Best Practices
1. ✅ Add both E2E and ARIA attributes to every interactive element
2. ✅ Keep attributes close together in the HTML for readability
3. ✅ Update tests to use `data-what` and `data-which` selectors
4. ✅ Validate coverage: all interactive elements should have both types
5. ✅ Review with QA and accessibility teams
## Detailed References
For comprehensive guides, examples, and patterns, see:
- **[E2E Testing Attributes](references/e2e-attributes.md)** - Complete E2E attribute patterns and conventions
- **[ARIA Accessibility Attributes](references/aria-attributes.md)** - Comprehensive ARIA guidance and WCAG compliance
- **[Combined Patterns](references/combined-patterns.md)** - Real-world examples with both attribute types
## Project-Specific Links
- **Testing Guidelines**: `docs/guidelines/testing.md` - Project testing standards including E2E attributes
- **CLAUDE.md**: Project conventions and requirements
- **Angular Template Skill**: `.claude/skills/angular-template` - For Angular-specific syntax
## Validation Checklist
Before considering template complete:
- [ ] All buttons have `data-what`, `data-which`, and `aria-label`
- [ ] All inputs have `data-what`, `data-which`, and appropriate ARIA attributes
- [ ] All links have `data-what`, `data-which`, and descriptive ARIA labels
- [ ] Dynamic lists use `[attr.data-*]` bindings with unique identifiers
- [ ] Dialogs have proper ARIA roles and relationships
- [ ] Forms have proper field associations and error announcements
- [ ] Interactive elements are keyboard accessible (tabindex where needed)
- [ ] No duplicate `data-which` values within the same view
- [ ] Screen reader testing completed (if applicable)
## Example: Complete Form
```html
<form
data-what="registration-form"
data-which="user-signup"
role="form"
aria-labelledby="form-title">
<h2 id="form-title">User Registration</h2>
<div class="form-field">
<label for="username-input">Username</label>
<input
id="username-input"
type="text"
[(ngModel)]="username"
data-what="username-input"
data-which="registration-form"
aria-required="true"
aria-describedby="username-hint" />
<span id="username-hint">Must be at least 3 characters</span>
</div>
<div class="form-field">
<label for="email-input">Email</label>
<input
id="email-input"
type="email"
[(ngModel)]="email"
data-what="email-input"
data-which="registration-form"
aria-required="true"
[attr.aria-invalid]="emailError ? 'true' : null"
aria-describedby="email-error" />
@if (emailError) {
<span
id="email-error"
role="alert"
aria-live="polite">
{{ emailError }}
</span>
}
</div>
<div class="form-actions">
<button
type="submit"
(click)="onSubmit()"
data-what="submit-button"
data-which="registration-form"
[attr.aria-disabled]="!isValid"
aria-label="Submit registration form">
Register
</button>
<button
type="button"
(click)="onCancel()"
data-what="cancel-button"
data-which="registration-form"
aria-label="Cancel registration">
Cancel
</button>
</div>
</form>
```
## Remember
- **Always use both E2E and ARIA attributes together**
- **E2E attributes enable automated testing** - your QA team relies on them
- **ARIA attributes enable accessibility** - legal requirement and right thing to do
- **Test with real users and assistive technologies** - automated checks aren't enough
- **Keep attributes up-to-date** - maintain as code changes
---
**This skill works automatically with Angular templates. Both E2E and ARIA attributes should be added to every interactive element.**

View File

File diff suppressed because it is too large Load Diff

View File

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,842 @@
# E2E Testing Attributes - Complete Reference
This reference provides comprehensive guidance for adding E2E (End-to-End) testing attributes to HTML templates for reliable automated testing.
## Table of Contents
- [Overview](#overview)
- [Core Attribute Types](#core-attribute-types)
- [Why E2E Attributes?](#why-e2e-attributes)
- [Naming Conventions](#naming-conventions)
- [Patterns by Element Type](#patterns-by-element-type)
- [Patterns by Component Type](#patterns-by-component-type)
- [Dynamic Attributes](#dynamic-attributes)
- [Best Practices](#best-practices)
- [Validation](#validation)
- [Testing Integration](#testing-integration)
## Overview
E2E testing attributes provide stable, semantic selectors for automated testing. They enable QA automation without relying on brittle CSS classes, IDs, or XPath selectors that frequently break when styling changes.
## Core Attribute Types
### 1. `data-what` (Required)
**Purpose**: Semantic description of the element's purpose or type
**Format**: kebab-case string
**Examples**:
- `data-what="submit-button"`
- `data-what="search-input"`
- `data-what="product-link"`
- `data-what="list-item"`
**Guidelines**:
- Describes WHAT the element is or does
- Should be consistent across similar elements
- Use descriptive, semantic names
- Keep it concise but clear
### 2. `data-which` (Required)
**Purpose**: Unique identifier for the specific instance of this element type
**Format**: kebab-case string or dynamic binding
**Examples**:
- `data-which="primary"` (static)
- `data-which="customer-form"` (static)
- `[attr.data-which]="item.id"` (dynamic)
- `[attr.data-which]="'customer-' + customerId"` (dynamic with context)
**Guidelines**:
- Identifies WHICH specific instance of this element type
- Must be unique within the same view/component
- Use dynamic binding for list items: `[attr.data-which]="item.id"`
- Can combine multiple identifiers: `data-which="customer-123-edit"`
### 3. `data-*` (Contextual)
**Purpose**: Additional contextual information about state, status, or data
**Format**: Custom attributes with kebab-case names
**Examples**:
- `data-status="active"`
- `data-index="0"`
- `data-role="admin"`
- `[attr.data-count]="items.length"`
**Guidelines**:
- Use for additional context that helps testing
- Avoid sensitive data (passwords, tokens, PII)
- Use Angular binding for dynamic values: `[attr.data-*]`
- Keep attribute names semantic and clear
## Why E2E Attributes?
### Problems with Traditional Selectors
**CSS Classes (Bad)**:
```html
<!-- Brittle - breaks when styling changes -->
<button class="btn btn-primary submit">Submit</button>
```
```javascript
// Test breaks when class names change
await page.click('.btn-primary.submit');
```
**XPath (Bad)**:
```javascript
// Brittle - breaks when structure changes
await page.click('//div[@class="form"]/button[2]');
```
**IDs (Better, but limited)**:
```html
<!-- IDs must be unique across entire page -->
<button id="submit-btn">Submit</button>
```
### Benefits of E2E Attributes
**Stable, Semantic Selectors (Good)**:
```html
<button
class="btn btn-primary"
data-what="submit-button"
data-which="registration-form">
Submit
</button>
```
```javascript
// Stable - survives styling and structure changes
await page.click('[data-what="submit-button"][data-which="registration-form"]');
```
**Advantages**:
- ✅ Decoupled from styling (CSS classes can change freely)
- ✅ Semantic and self-documenting
- ✅ Consistent across the application
- ✅ Easy to read and maintain
- ✅ Survives refactoring and restructuring
- ✅ QA and developers speak the same language
## Naming Conventions
### Common `data-what` Patterns
| Pattern | Use Case | Examples |
|---------|----------|----------|
| `*-button` | All button elements | `submit-button`, `cancel-button`, `delete-button`, `save-button` |
| `*-input` | Text inputs and textareas | `email-input`, `search-input`, `quantity-input`, `password-input` |
| `*-select` | Dropdown/select elements | `status-select`, `category-select`, `country-select` |
| `*-checkbox` | Checkbox inputs | `terms-checkbox`, `subscribe-checkbox`, `remember-checkbox` |
| `*-radio` | Radio button inputs | `payment-radio`, `shipping-radio` |
| `*-link` | Navigation links | `product-link`, `order-link`, `customer-link`, `home-link` |
| `*-item` | List/grid items | `list-item`, `menu-item`, `card-item`, `row-item` |
| `*-dialog` | Modals and dialogs | `confirm-dialog`, `error-dialog`, `info-dialog` |
| `*-dropdown` | Dropdown menus | `actions-dropdown`, `filter-dropdown` |
| `*-toggle` | Toggle switches | `theme-toggle`, `notifications-toggle` |
| `*-tab` | Tab navigation | `profile-tab`, `settings-tab` |
| `*-badge` | Status badges | `status-badge`, `count-badge` |
| `*-icon` | Interactive icons | `close-icon`, `menu-icon`, `search-icon` |
### `data-which` Naming Guidelines
**Static unique identifiers** (single instance):
- `data-which="primary"` - Primary action button
- `data-which="secondary"` - Secondary action button
- `data-which="main-search"` - Main search input
- `data-which="customer-form"` - Customer form context
**Dynamic identifiers** (multiple instances):
- `[attr.data-which]="item.id"` - List item by ID
- `[attr.data-which]="'product-' + product.id"` - Product item
- `[attr.data-which]="index"` - By array index (use sparingly)
**Contextual identifiers** (combine context):
- `data-which="customer-{{ customerId }}-edit"` - Edit button for specific customer
- `data-which="order-{{ orderId }}-cancel"` - Cancel button for specific order
## Patterns by Element Type
### Buttons
```html
<!-- Submit Button -->
<button
type="submit"
(click)="onSubmit()"
data-what="submit-button"
data-which="registration-form">
Submit
</button>
<!-- Cancel Button -->
<button
type="button"
(click)="onCancel()"
data-what="cancel-button"
data-which="registration-form">
Cancel
</button>
<!-- Delete Button with Confirmation -->
<button
(click)="onDelete(item)"
data-what="delete-button"
[attr.data-which]="item.id"
[attr.data-status]="item.canDelete ? 'enabled' : 'disabled'">
Delete
</button>
<!-- Icon Button -->
<button
(click)="toggleMenu()"
data-what="menu-button"
data-which="main-nav"
aria-label="Toggle menu">
<i class="icon-menu"></i>
</button>
<!-- Custom Button Component -->
<ui-button
(click)="save()"
data-what="save-button"
data-which="order-form">
Save Order
</ui-button>
```
### Inputs
```html
<!-- Text Input -->
<input
type="text"
[(ngModel)]="email"
placeholder="Email address"
data-what="email-input"
data-which="registration-form" />
<!-- Textarea -->
<textarea
[(ngModel)]="comments"
data-what="comments-textarea"
data-which="feedback-form"
rows="4"></textarea>
<!-- Number Input with State -->
<input
type="number"
[(ngModel)]="quantity"
data-what="quantity-input"
data-which="order-form"
[attr.data-min]="minQuantity"
[attr.data-max]="maxQuantity" />
<!-- Search Input -->
<input
type="search"
[(ngModel)]="searchTerm"
(input)="onSearch()"
placeholder="Search products..."
data-what="search-input"
data-which="product-catalog" />
<!-- Password Input -->
<input
type="password"
[(ngModel)]="password"
data-what="password-input"
data-which="login-form" />
```
### Select/Dropdown
```html
<!-- Basic Select -->
<select
[(ngModel)]="selectedStatus"
data-what="status-select"
data-which="order-filter">
<option value="">All Statuses</option>
<option value="pending">Pending</option>
<option value="completed">Completed</option>
</select>
<!-- Custom Dropdown Component -->
<ui-dropdown
[(value)]="selectedCategory"
data-what="category-dropdown"
data-which="product-filter">
</ui-dropdown>
```
### Checkboxes and Radios
```html
<!-- Checkbox -->
<label>
<input
type="checkbox"
[(ngModel)]="agreedToTerms"
data-what="terms-checkbox"
data-which="registration-form" />
I agree to the terms
</label>
<!-- Radio Group -->
<div data-what="payment-radio-group" data-which="checkout-form">
<label>
<input
type="radio"
name="payment"
value="credit"
[(ngModel)]="paymentMethod"
data-what="payment-radio"
data-which="credit-card" />
Credit Card
</label>
<label>
<input
type="radio"
name="payment"
value="paypal"
[(ngModel)]="paymentMethod"
data-what="payment-radio"
data-which="paypal" />
PayPal
</label>
</div>
```
### Links
```html
<!-- Static Link -->
<a
routerLink="/about"
data-what="nav-link"
data-which="about">
About Us
</a>
<!-- Dynamic Link with ID -->
<a
[routerLink]="['/products', product.id]"
data-what="product-link"
[attr.data-which]="product.id">
{{ product.name }}
</a>
<!-- External Link -->
<a
href="https://example.com"
target="_blank"
data-what="external-link"
data-which="documentation">
Documentation
</a>
<!-- Action Link (not navigation) -->
<a
(click)="downloadReport()"
data-what="download-link"
data-which="sales-report">
Download Report
</a>
```
### Lists and Tables
```html
<!-- Dynamic List with @for -->
<ul data-what="product-list" data-which="catalog">
@for (product of products; track product.id) {
<li
(click)="selectProduct(product)"
data-what="list-item"
[attr.data-which]="product.id"
[attr.data-status]="product.stock > 0 ? 'in-stock' : 'out-of-stock'">
{{ product.name }}
</li>
}
</ul>
<!-- Table Row -->
<table data-what="orders-table" data-which="customer-orders">
<tbody>
@for (order of orders; track order.id) {
<tr
data-what="table-row"
[attr.data-which]="order.id">
<td>{{ order.id }}</td>
<td>{{ order.date }}</td>
<td>
<button
data-what="view-button"
[attr.data-which]="order.id">
View
</button>
</td>
</tr>
}
</tbody>
</table>
```
### Dialogs and Modals
```html
<!-- Confirmation Dialog -->
<div
*ngIf="showDialog"
data-what="confirmation-dialog"
data-which="delete-item">
<h2>Confirm Deletion</h2>
<p>Are you sure you want to delete this item?</p>
<button
(click)="confirmDelete()"
data-what="confirm-button"
data-which="delete-dialog">
Delete
</button>
<button
(click)="cancelDelete()"
data-what="cancel-button"
data-which="delete-dialog">
Cancel
</button>
</div>
<!-- Info Dialog with Close -->
<div
data-what="info-dialog"
data-which="welcome-message">
<button
(click)="closeDialog()"
data-what="close-button"
data-which="dialog">
×
</button>
<div data-what="dialog-content" data-which="welcome">
<h2>Welcome!</h2>
<p>Thank you for joining us.</p>
</div>
</div>
```
## Patterns by Component Type
### Form Components
```html
<form data-what="user-form" data-which="registration">
<!-- Field inputs -->
<input
data-what="username-input"
data-which="registration-form"
type="text" />
<input
data-what="email-input"
data-which="registration-form"
type="email" />
<!-- Action buttons -->
<button
data-what="submit-button"
data-which="registration-form"
type="submit">
Submit
</button>
<button
data-what="cancel-button"
data-which="registration-form"
type="button">
Cancel
</button>
</form>
```
### List/Table Components
```html
<!-- Each item needs unique data-which -->
@for (item of items; track item.id) {
<div
data-what="list-item"
[attr.data-which]="item.id">
<span data-what="item-name" [attr.data-which]="item.id">
{{ item.name }}
</span>
<button
data-what="edit-button"
[attr.data-which]="item.id">
Edit
</button>
<button
data-what="delete-button"
[attr.data-which]="item.id">
Delete
</button>
</div>
}
```
### Navigation Components
```html
<nav data-what="main-navigation" data-which="header">
<a
routerLink="/dashboard"
data-what="nav-link"
data-which="dashboard">
Dashboard
</a>
<a
routerLink="/orders"
data-what="nav-link"
data-which="orders">
Orders
</a>
<a
routerLink="/customers"
data-what="nav-link"
data-which="customers">
Customers
</a>
</nav>
<!-- Breadcrumbs -->
<nav data-what="breadcrumb" data-which="page-navigation">
@for (crumb of breadcrumbs; track $index) {
<a
[routerLink]="crumb.url"
data-what="breadcrumb-link"
[attr.data-which]="crumb.id">
{{ crumb.label }}
</a>
}
</nav>
```
### Dialog/Modal Components
```html
<!-- All dialog buttons need clear identifiers -->
<div data-what="modal" data-which="user-settings">
<button
data-what="close-button"
data-which="modal">
Close
</button>
<button
data-what="save-button"
data-which="modal">
Save Changes
</button>
<button
data-what="reset-button"
data-which="modal">
Reset to Defaults
</button>
</div>
```
## Dynamic Attributes
### Using Angular Binding
When values need to be dynamic, use Angular's attribute binding:
```html
<!-- Static (simple values) -->
<button data-what="submit-button" data-which="form">
<!-- Dynamic (from component properties) -->
<button
data-what="submit-button"
[attr.data-which]="formId">
<!-- Dynamic (from loop variables) -->
@for (item of items; track item.id) {
<div
data-what="list-item"
[attr.data-which]="item.id"
[attr.data-status]="item.status"
[attr.data-index]="$index">
</div>
}
<!-- Dynamic (computed values) -->
<button
data-what="action-button"
[attr.data-which]="'customer-' + customerId + '-' + action">
</button>
```
### Loop Variables
Angular's `@for` provides special variables:
```html
@for (item of items; track item.id; let idx = $index; let isFirst = $first) {
<div
data-what="list-item"
[attr.data-which]="item.id"
[attr.data-index]="idx"
[attr.data-first]="isFirst">
{{ item.name }}
</div>
}
```
## Best Practices
### Do's ✅
1. **Add to ALL interactive elements**
- Buttons, inputs, links, clickable elements
- Custom components that handle user interaction
- Form controls and navigation items
2. **Use consistent naming**
- Follow the naming patterns (e.g., `*-button`, `*-input`)
- Use kebab-case consistently
- Be descriptive but concise
3. **Ensure uniqueness**
- `data-which` must be unique within the view
- Use item IDs for list items: `[attr.data-which]="item.id"`
- Combine context when needed: `data-which="form-primary-submit"`
4. **Use Angular binding for dynamic values**
- `[attr.data-which]="item.id"`
- `data-which="{{ item.id }}"` ❌ (avoid interpolation)
5. **Document complex patterns**
- Add comments for non-obvious attribute choices
- Document the expected test selectors
6. **Keep attributes updated**
- Update when element purpose changes
- Remove when elements are removed
- Maintain consistency across refactoring
### Don'ts ❌
1. **Don't include sensitive data**
-`data-which="password-{{ userPassword }}"`
-`data-token="{{ authToken }}"`
-`data-ssn="{{ socialSecurity }}"`
2. **Don't use generic values**
-`data-what="button"` (too generic)
-`data-what="submit-button"` (specific)
3. **Don't duplicate `data-which` in the same view**
- ❌ Two buttons with `data-which="primary"`
-`data-which="form-primary"` and `data-which="dialog-primary"`
4. **Don't rely only on index for lists**
-`[attr.data-which]="$index"` (changes when list reorders)
-`[attr.data-which]="item.id"` (stable identifier)
5. **Don't forget about custom components**
- Custom components need attributes too
- Attributes should be on the component tag, not just internal elements
## Validation
### Coverage Check
Ensure all interactive elements have E2E attributes:
```bash
# Count interactive elements
grep -E '\(click\)|routerLink|button|input|select|textarea' component.html | wc -l
# Count elements with data-what
grep -c 'data-what=' component.html
# Find elements missing E2E attributes
grep -E '\(click\)|button' component.html | grep -v 'data-what='
```
### Uniqueness Check
Verify no duplicate `data-which` values in the same template:
```typescript
// In component tests
it('should have unique data-which attributes', () => {
const elements = fixture.nativeElement.querySelectorAll('[data-which]');
const dataWhichValues = Array.from(elements).map(
(el: any) => el.getAttribute('data-which')
);
const uniqueValues = new Set(dataWhichValues);
expect(dataWhichValues.length).toBe(uniqueValues.size);
});
```
### Validation Checklist
- [ ] All buttons have `data-what` and `data-which`
- [ ] All inputs have `data-what` and `data-which`
- [ ] All links have `data-what` and `data-which`
- [ ] All clickable elements have attributes
- [ ] Dynamic lists use `[attr.data-which]="item.id"`
- [ ] No duplicate `data-which` values in the same view
- [ ] No sensitive data in attributes
- [ ] Custom components have attributes
- [ ] Attributes use kebab-case
- [ ] Coverage: 100% of interactive elements
## Testing Integration
### Using E2E Attributes in Tests
**Unit Tests (Angular Testing Utilities)**:
```typescript
import { ComponentFixture, TestBed } from '@angular/core/testing';
describe('MyComponent', () => {
let fixture: ComponentFixture<MyComponent>;
beforeEach(async () => {
await TestBed.configureTestingModule({
imports: [MyComponent],
}).compileComponents();
fixture = TestBed.createComponent(MyComponent);
fixture.detectChanges();
});
it('should have submit button with E2E attributes', () => {
const button = fixture.nativeElement.querySelector(
'[data-what="submit-button"][data-which="registration-form"]'
);
expect(button).toBeTruthy();
expect(button.textContent).toContain('Submit');
});
it('should have unique data-which for list items', () => {
const items = fixture.nativeElement.querySelectorAll('[data-what="list-item"]');
const dataWhichValues = Array.from(items).map(
(item: any) => item.getAttribute('data-which')
);
// All should have unique IDs
const uniqueValues = new Set(dataWhichValues);
expect(dataWhichValues.length).toBe(uniqueValues.size);
});
});
```
**E2E Tests (Playwright)**:
```typescript
import { test, expect } from '@playwright/test';
test('user registration flow', async ({ page }) => {
await page.goto('/register');
// Fill form using E2E attributes
await page.fill(
'[data-what="username-input"][data-which="registration-form"]',
'johndoe'
);
await page.fill(
'[data-what="email-input"][data-which="registration-form"]',
'john@example.com'
);
// Click submit using E2E attributes
await page.click(
'[data-what="submit-button"][data-which="registration-form"]'
);
// Verify success
await expect(page.locator('[data-what="success-message"]')).toBeVisible();
});
```
**E2E Tests (Cypress)**:
```typescript
describe('Order Management', () => {
it('should edit an order', () => {
cy.visit('/orders');
// Find specific order by ID using data-which
cy.get('[data-what="list-item"][data-which="order-123"]')
.should('be.visible');
// Click edit button for that specific order
cy.get('[data-what="edit-button"][data-which="order-123"]')
.click();
// Update quantity
cy.get('[data-what="quantity-input"][data-which="order-form"]')
.clear()
.type('5');
// Save changes
cy.get('[data-what="save-button"][data-which="order-form"]')
.click();
});
});
```
## Documentation in Templates
Add comment blocks to document E2E attributes:
```html
<!--
E2E Test Attributes:
- data-what="submit-button" data-which="registration-form" - Main form submission
- data-what="cancel-button" data-which="registration-form" - Cancel registration
- data-what="username-input" data-which="registration-form" - Username field
- data-what="email-input" data-which="registration-form" - Email field
- data-what="password-input" data-which="registration-form" - Password field
-->
<form data-what="registration-form" data-which="user-signup">
<!-- Form content -->
</form>
```
## Related Documentation
- **[ARIA Accessibility Attributes](aria-attributes.md)** - Accessibility guidance
- **[Combined Patterns](combined-patterns.md)** - Examples with E2E + ARIA together
- **Testing Guidelines**: `docs/guidelines/testing.md` - Project testing standards
- **CLAUDE.md**: Project code quality requirements
## Summary
E2E testing attributes are essential for:
- ✅ Stable, maintainable automated tests
- ✅ Clear communication between developers and QA
- ✅ Tests that survive styling and structural changes
- ✅ Self-documenting code that expresses intent
- ✅ Reliable CI/CD pipelines
**Always add `data-what` and `data-which` to every interactive element.**

View File

@@ -1,6 +1,6 @@
---
name: library-scaffolder
description: This skill should be used when creating new Angular libraries in the ISA-Frontend monorepo. It handles Nx library generation with proper naming conventions, Vitest configuration with JUnit/Cobertura reporters, path alias setup, and validation. Use this skill when the user wants to create a new library, scaffold a feature/data-access/ui/util library, or requests "new library" creation.
description: This skill should be used when creating feature/data-access/ui/util libraries or user says "create library", "new library", "scaffold library". Creates new Angular libraries in ISA-Frontend monorepo with proper Nx configuration, Vitest setup, architectural tags, and path aliases.
---
# Library Scaffolder
@@ -51,6 +51,7 @@ npx nx generate @nx/angular:library \
--name=[domain]-[layer]-[name] \
--directory=libs/[domain]/[layer]/[name] \
--importPath=@isa/[domain]/[layer]/[name] \
--prefix=[domain] \
--style=css \
--unitTestRunner=vitest \
--standalone=true \
@@ -69,13 +70,53 @@ npx nx generate @nx/angular:library \
--name=[domain]-[layer]-[name] \
--directory=libs/[domain]/[layer]/[name] \
--importPath=@isa/[domain]/[layer]/[name] \
--prefix=[domain] \
--style=css \
--unitTestRunner=vitest \
--standalone=true \
--skipTests=false
```
### Step 4: Configure Vitest with JUnit and Cobertura
### Step 4: Add Architectural Tags
**CRITICAL**: Immediately after library generation, add proper tags to `project.json` for `@nx/enforce-module-boundaries`.
Run the tagging script:
```bash
node scripts/add-library-tags.js
```
Or manually add tags to `libs/[domain]/[layer]/[name]/project.json`:
```json
{
"name": "[domain]-[layer]-[name]",
"tags": [
"scope:[domain]",
"type:[layer]"
]
}
```
**Tag Rules:**
- **Scope tag**: `scope:[domain]` (e.g., `scope:oms`, `scope:crm`, `scope:ui`, `scope:shared`)
- **Type tag**: `type:[layer]` (e.g., `type:feature`, `type:data-access`, `type:ui`, `type:util`)
**Examples:**
- `libs/oms/feature/return-search``["scope:oms", "type:feature"]`
- `libs/ui/buttons``["scope:ui", "type:ui"]`
- `libs/shared/scanner``["scope:shared", "type:shared"]`
- `libs/core/auth``["scope:core", "type:core"]`
**Verification:**
```bash
# Check tags were added
cat libs/[domain]/[layer]/[name]/project.json | jq '.tags'
# Should output: ["scope:[domain]", "type:[layer]"]
```
### Step 5: Configure Vitest with JUnit and Cobertura
Update `libs/[path]/vite.config.mts`:
@@ -113,7 +154,7 @@ defineConfig(() => ({
**Critical**: Adjust path depth based on library location.
### Step 5: Verify Configuration
### Step 6: Verify Configuration
1. **Check Path Alias**
- Verify `tsconfig.base.json` was updated
@@ -128,7 +169,7 @@ defineConfig(() => ({
- JUnit XML: `testresults/junit-[library-name].xml`
- Cobertura XML: `coverage/libs/[path]/cobertura-coverage.xml`
### Step 6: Create Library README
### Step 7: Create Library README
Use `docs-researcher` to find similar library READMEs, then create comprehensive documentation including:
- Overview and purpose
@@ -137,7 +178,7 @@ Use `docs-researcher` to find similar library READMEs, then create comprehensive
- Usage examples
- Testing information (Vitest + Angular Testing Utilities)
### Step 7: Update Library Reference
### Step 8: Update Library Reference
Add entry to `docs/library-reference.md` under appropriate domain:
@@ -150,10 +191,10 @@ Add entry to `docs/library-reference.md` under appropriate domain:
[Brief description]
```
### Step 8: Run Full Validation
### Step 9: Run Full Validation
```bash
# Lint
# Lint (includes boundary checks)
npx nx lint [library-name]
# Test with coverage
@@ -166,7 +207,7 @@ npx nx build [library-name]
npx nx graph --focus=[library-name]
```
### Step 9: Generate Creation Report
### Step 10: Generate Creation Report
```
Library Created Successfully
@@ -181,6 +222,7 @@ Import Alias: @isa/[domain]/[layer]/[name]
Test Framework: Vitest with Angular Testing Utilities
Style: CSS
Standalone: Yes
Tags: scope:[domain], type:[layer]
JUnit Reporter: ✅ testresults/junit-[library-name].xml
Cobertura Coverage: ✅ coverage/libs/[path]/cobertura-coverage.xml
@@ -193,12 +235,18 @@ import { Component } from '@isa/[domain]/[layer]/[name]';
npx nx test [library-name] --skip-nx-cache
npx nx test [library-name] --coverage.enabled=true --skip-nx-cache
🏗️ Architecture Compliance
--------------------------
Tags enforce module boundaries via @nx/enforce-module-boundaries
Run lint to check for violations: npx nx lint [library-name]
📝 Next Steps
-------------
1. Develop library features
2. Write tests using Vitest + Angular Testing Utilities
3. Add E2E attributes (data-what, data-which) to templates
4. Update README with usage examples
5. Follow architecture rules (see eslint.config.js for constraints)
```
## Error Handling
@@ -220,4 +268,8 @@ npx nx test [library-name] --coverage.enabled=true --skip-nx-cache
- docs/guidelines/testing.md (Vitest, JUnit, Cobertura sections)
- docs/library-reference.md (domain patterns)
- CLAUDE.md (Library Organization, Testing Framework sections)
- eslint.config.js (@nx/enforce-module-boundaries configuration)
- scripts/add-library-tags.js (automatic tagging script)
- .claude/skills/architecture-enforcer (boundary validation)
- Nx Angular Library Generator: https://nx.dev/nx-api/angular/generators/library
- Nx Enforce Module Boundaries: https://nx.dev/nx-api/eslint-plugin/documents/enforce-module-boundaries

View File

@@ -0,0 +1,272 @@
---
name: logging
description: This skill should be used when working with Angular components, directives, services, pipes, guards, or TypeScript classes. Logging is MANDATORY in all Angular files. Implements @isa/core/logging with logger() factory pattern, appropriate log levels, lazy evaluation for performance, error handling, and avoids console.log and common mistakes.
---
# Logging Helper Skill
Ensures consistent and efficient logging using `@isa/core/logging` library.
## When to Use
- Adding logging to new components/services
- Refactoring existing logging code
- Reviewing code for proper logging patterns
- Debugging logging issues
## Core Principles
### 1. Always Use Factory Pattern
```typescript
import { logger } from '@isa/core/logging';
// ✅ DO
#logger = logger();
// ❌ DON'T
constructor(private loggingService: LoggingService) {}
```
### 2. Choose Appropriate Log Levels
- **Trace**: Fine-grained debugging (method entry/exit)
- **Debug**: Development debugging (variable states)
- **Info**: Runtime information (user actions, events)
- **Warn**: Potentially harmful situations
- **Error**: Errors affecting functionality
### 3. Context Patterns
**Static Context** (component level):
```typescript
#logger = logger({ component: 'UserProfileComponent' });
```
**Dynamic Context** (instance level):
```typescript
#logger = logger(() => ({
userId: this.authService.currentUserId,
storeId: this.config.storeId
}));
```
**Message Context** (use functions for performance):
```typescript
// ✅ Recommended - lazy evaluation
this.#logger.info('Order processed', () => ({
orderId: order.id,
total: order.total,
timestamp: Date.now()
}));
// ✅ Acceptable - static values
this.#logger.info('Order processed', {
orderId: order.id,
status: 'completed'
});
```
## Essential Patterns
### Component Logging
```typescript
@Component({
selector: 'app-product-list',
standalone: true,
})
export class ProductListComponent {
#logger = logger({ component: 'ProductListComponent' });
ngOnInit(): void {
this.#logger.info('Component initialized');
}
onAction(id: string): void {
this.#logger.debug('Action triggered', { id });
}
}
```
### Service Logging
```typescript
@Injectable({ providedIn: 'root' })
export class DataService {
#logger = logger({ service: 'DataService' });
fetchData(endpoint: string): Observable<Data> {
this.#logger.debug('Fetching data', { endpoint });
return this.http.get<Data>(endpoint).pipe(
tap((data) => this.#logger.info('Data fetched', () => ({
endpoint,
size: data.length
}))),
catchError((error) => {
this.#logger.error('Fetch failed', error, () => ({
endpoint,
status: error.status
}));
return throwError(() => error);
})
);
}
}
```
### Error Handling
```typescript
try {
await this.processOrder(orderId);
} catch (error) {
this.#logger.error('Order processing failed', error as Error, () => ({
orderId,
step: this.currentStep,
attemptNumber: this.retryCount
}));
throw error;
}
```
### Hierarchical Context
```typescript
@Component({
providers: [
provideLoggerContext({ feature: 'checkout', module: 'sales' })
]
})
export class CheckoutComponent {
#logger = logger(() => ({ userId: this.userService.currentUserId }));
// Logs include: feature, module, userId + message context
}
```
## Common Mistakes to Avoid
```typescript
// ❌ Don't use console.log
console.log('User logged in');
// ✅ Use logger
this.#logger.info('User logged in');
// ❌ Don't create expensive context eagerly
this.#logger.debug('Processing', {
data: this.computeExpensive() // Always executes
});
// ✅ Use function for lazy evaluation
this.#logger.debug('Processing', () => ({
data: this.computeExpensive() // Only if debug enabled
}));
// ❌ Don't log in tight loops
for (const item of items) {
this.#logger.debug('Item', { item });
}
// ✅ Log aggregates
this.#logger.debug('Batch processed', () => ({
count: items.length
}));
// ❌ Don't log sensitive data
this.#logger.info('User auth', { password: user.password });
// ✅ Log safe identifiers only
this.#logger.info('User auth', { userId: user.id });
// ❌ Don't miss error object
this.#logger.error('Failed');
// ✅ Include error object
this.#logger.error('Failed', error as Error);
```
## Configuration
### App Configuration
```typescript
// app.config.ts
import { ApplicationConfig, isDevMode } from '@angular/core';
import {
provideLogging, withLogLevel, withSink,
LogLevel, ConsoleLogSink
} from '@isa/core/logging';
export const appConfig: ApplicationConfig = {
providers: [
provideLogging(
withLogLevel(isDevMode() ? LogLevel.Debug : LogLevel.Warn),
withSink(ConsoleLogSink),
withContext({ app: 'ISA', version: '1.0.0' })
)
]
};
```
## Testing
```typescript
import { createComponentFactory, Spectator } from '@ngneat/spectator/jest';
import { LoggingService } from '@isa/core/logging';
describe('MyComponent', () => {
const createComponent = createComponentFactory({
component: MyComponent,
mocks: [LoggingService]
});
it('should log error', () => {
const spectator = createComponent();
const loggingService = spectator.inject(LoggingService);
spectator.component.riskyOperation();
expect(loggingService.error).toHaveBeenCalledWith(
expect.any(String),
expect.any(Error),
expect.any(Function)
);
});
});
```
## Code Review Checklist
- [ ] Uses `logger()` factory, not `LoggingService` injection
- [ ] Appropriate log level for each message
- [ ] Context functions for expensive operations
- [ ] No sensitive information (passwords, tokens, PII)
- [ ] No `console.log` statements
- [ ] Error logs include error object
- [ ] No logging in tight loops
- [ ] Component/service identified in context
- [ ] E2E attributes on interactive elements
## Quick Reference
```typescript
// Import
import { logger, provideLoggerContext } from '@isa/core/logging';
// Create logger
#logger = logger(); // Basic
#logger = logger({ component: 'Name' }); // Static context
#logger = logger(() => ({ id: this.id })); // Dynamic context
// Log messages
this.#logger.trace('Detailed trace');
this.#logger.debug('Debug info');
this.#logger.info('General info', () => ({ key: value }));
this.#logger.warn('Warning');
this.#logger.error('Error', error, () => ({ context }));
// Component context
@Component({
providers: [provideLoggerContext({ feature: 'users' })]
})
```
## Additional Resources
- Full documentation: `libs/core/logging/README.md`
- Examples: `.claude/skills/logging-helper/examples.md`
- Quick reference: `.claude/skills/logging-helper/reference.md`
- Troubleshooting: `.claude/skills/logging-helper/troubleshooting.md`

View File

@@ -0,0 +1,350 @@
# Logging Examples
Concise real-world examples of logging patterns.
## 1. Component with Observable
```typescript
import { Component, OnInit } from '@angular/core';
import { logger } from '@isa/core/logging';
@Component({
selector: 'app-product-list',
standalone: true,
})
export class ProductListComponent implements OnInit {
#logger = logger({ component: 'ProductListComponent' });
constructor(private productService: ProductService) {}
ngOnInit(): void {
this.#logger.info('Component initialized');
this.loadProducts();
}
private loadProducts(): void {
this.productService.getProducts().subscribe({
next: (products) => {
this.#logger.info('Products loaded', () => ({ count: products.length }));
},
error: (error) => {
this.#logger.error('Failed to load products', error);
}
});
}
}
```
## 2. Service with HTTP
```typescript
import { Injectable, inject } from '@angular/core';
import { HttpClient } from '@angular/common/http';
import { logger } from '@isa/core/logging';
import { catchError, tap } from 'rxjs/operators';
@Injectable({ providedIn: 'root' })
export class OrderService {
private http = inject(HttpClient);
#logger = logger({ service: 'OrderService' });
getOrder(id: string): Observable<Order> {
this.#logger.debug('Fetching order', { id });
return this.http.get<Order>(`/api/orders/${id}`).pipe(
tap((order) => this.#logger.info('Order fetched', () => ({
id,
status: order.status
}))),
catchError((error) => {
this.#logger.error('Fetch failed', error, () => ({ id, status: error.status }));
throw error;
})
);
}
}
```
## 3. Hierarchical Context
```typescript
import { Component } from '@angular/core';
import { logger, provideLoggerContext } from '@isa/core/logging';
@Component({
selector: 'oms-return-process',
standalone: true,
providers: [
provideLoggerContext({ feature: 'returns', module: 'oms' })
],
})
export class ReturnProcessComponent {
#logger = logger(() => ({
processId: this.currentProcessId,
step: this.currentStep
}));
private currentProcessId = crypto.randomUUID();
private currentStep = 1;
startProcess(orderId: string): void {
// Logs include: feature, module, processId, step, orderId
this.#logger.info('Process started', { orderId });
}
}
```
## 4. NgRx Effect
```typescript
import { Injectable } from '@angular/core';
import { Actions, createEffect, ofType } from '@ngrx/effects';
import { logger } from '@isa/core/logging';
import { map, catchError, tap } from 'rxjs/operators';
import { of } from 'rxjs';
@Injectable()
export class OrdersEffects {
#logger = logger({ effect: 'OrdersEffects' });
loadOrders$ = createEffect(() =>
this.actions$.pipe(
ofType(OrdersActions.loadOrders),
tap((action) => this.#logger.debug('Loading orders', () => ({
page: action.page
}))),
mergeMap((action) =>
this.orderService.getOrders(action.filters).pipe(
map((orders) => {
this.#logger.info('Orders loaded', () => ({ count: orders.length }));
return OrdersActions.loadOrdersSuccess({ orders });
}),
catchError((error) => {
this.#logger.error('Load failed', error);
return of(OrdersActions.loadOrdersFailure({ error }));
})
)
)
)
);
constructor(
private actions$: Actions,
private orderService: OrderService
) {}
}
```
## 5. Guard with Authorization
```typescript
import { inject } from '@angular/core';
import { CanActivateFn, Router } from '@angular/router';
import { logger } from '@isa/core/logging';
export const authGuard: CanActivateFn = (route, state) => {
const authService = inject(AuthService);
const router = inject(Router);
const log = logger({ guard: 'AuthGuard' });
if (authService.isAuthenticated()) {
log.debug('Access granted', () => ({ route: state.url }));
return true;
}
log.warn('Access denied', () => ({
attemptedRoute: state.url,
redirectTo: '/login'
}));
return router.createUrlTree(['/login']);
};
```
## 6. HTTP Interceptor
```typescript
import { HttpInterceptorFn } from '@angular/common/http';
import { inject } from '@angular/core';
import { tap, catchError } from 'rxjs/operators';
import { LoggingService } from '@isa/core/logging';
export const loggingInterceptor: HttpInterceptorFn = (req, next) => {
const loggingService = inject(LoggingService);
const startTime = performance.now();
loggingService.debug('HTTP Request', () => ({
method: req.method,
url: req.url
}));
return next(req).pipe(
tap((event) => {
if (event.type === HttpEventType.Response) {
loggingService.info('HTTP Response', () => ({
method: req.method,
url: req.url,
status: event.status,
duration: `${(performance.now() - startTime).toFixed(2)}ms`
}));
}
}),
catchError((error) => {
loggingService.error('HTTP Error', error, () => ({
method: req.method,
url: req.url,
status: error.status
}));
return throwError(() => error);
})
);
};
```
## 7. Form Validation
```typescript
import { Component, OnInit } from '@angular/core';
import { FormBuilder, FormGroup, Validators } from '@angular/forms';
import { logger } from '@isa/core/logging';
@Component({
selector: 'shared-user-form',
standalone: true,
})
export class UserFormComponent implements OnInit {
#logger = logger({ component: 'UserFormComponent' });
form!: FormGroup;
constructor(private fb: FormBuilder) {}
ngOnInit(): void {
this.form = this.fb.group({
name: ['', Validators.required],
email: ['', [Validators.required, Validators.email]]
});
}
onSubmit(): void {
if (this.form.invalid) {
this.#logger.warn('Invalid form submission', () => ({
errors: this.getFormErrors()
}));
return;
}
this.#logger.info('Form submitted');
}
private getFormErrors(): Record<string, unknown> {
const errors: Record<string, unknown> = {};
Object.keys(this.form.controls).forEach((key) => {
const control = this.form.get(key);
if (control?.errors) errors[key] = control.errors;
});
return errors;
}
}
```
## 8. Async Progress Tracking
```typescript
import { Injectable } from '@angular/core';
import { logger } from '@isa/core/logging';
import { Observable } from 'rxjs';
import { tap } from 'rxjs/operators';
@Injectable({ providedIn: 'root' })
export class ImportService {
#logger = logger({ service: 'ImportService' });
importData(file: File): Observable<number> {
const importId = crypto.randomUUID();
this.#logger.info('Import started', () => ({
importId,
fileName: file.name,
fileSize: file.size
}));
return this.processImport(file).pipe(
tap((progress) => {
if (progress % 25 === 0) {
this.#logger.debug('Import progress', () => ({
importId,
progress: `${progress}%`
}));
}
}),
tap({
complete: () => this.#logger.info('Import completed', { importId }),
error: (error) => this.#logger.error('Import failed', error, { importId })
})
);
}
private processImport(file: File): Observable<number> {
// Implementation
}
}
```
## 9. Global Error Handler
```typescript
import { Injectable, ErrorHandler } from '@angular/core';
import { logger } from '@isa/core/logging';
@Injectable()
export class GlobalErrorHandler implements ErrorHandler {
#logger = logger({ handler: 'GlobalErrorHandler' });
handleError(error: Error): void {
this.#logger.error('Uncaught error', error, () => ({
url: window.location.href,
userAgent: navigator.userAgent,
timestamp: new Date().toISOString()
}));
}
}
```
## 10. WebSocket Component
```typescript
import { Component, OnInit, OnDestroy } from '@angular/core';
import { logger } from '@isa/core/logging';
import { Subject, takeUntil } from 'rxjs';
@Component({
selector: 'oms-live-orders',
standalone: true,
})
export class LiveOrdersComponent implements OnInit, OnDestroy {
#logger = logger({ component: 'LiveOrdersComponent' });
private destroy$ = new Subject<void>();
constructor(private wsService: WebSocketService) {}
ngOnInit(): void {
this.#logger.info('Connecting to WebSocket');
this.wsService.connect('orders').pipe(
takeUntil(this.destroy$)
).subscribe({
next: (msg) => this.#logger.debug('Message received', () => ({
type: msg.type,
orderId: msg.orderId
})),
error: (error) => this.#logger.error('WebSocket error', error),
complete: () => this.#logger.info('WebSocket closed')
});
}
ngOnDestroy(): void {
this.#logger.debug('Component destroyed');
this.destroy$.next();
this.destroy$.complete();
}
}
```

View File

@@ -0,0 +1,192 @@
# Logging Quick Reference
## API Signatures
```typescript
// Factory
function logger(ctx?: MaybeLoggerContextFn): LoggerApi
// Logger API
interface LoggerApi {
trace(message: string, context?: MaybeLoggerContextFn): void;
debug(message: string, context?: MaybeLoggerContextFn): void;
info(message: string, context?: MaybeLoggerContextFn): void;
warn(message: string, context?: MaybeLoggerContextFn): void;
error(message: string, error?: Error, context?: MaybeLoggerContextFn): void;
}
// Types
type MaybeLoggerContextFn = LoggerContext | (() => LoggerContext);
interface LoggerContext { [key: string]: unknown; }
```
## Common Patterns
| Pattern | Code |
|---------|------|
| Basic logger | `#logger = logger()` |
| Static context | `#logger = logger({ component: 'Name' })` |
| Dynamic context | `#logger = logger(() => ({ id: this.id }))` |
| Log info | `this.#logger.info('Message')` |
| Log with context | `this.#logger.info('Message', () => ({ key: value }))` |
| Log error | `this.#logger.error('Error', error)` |
| Error with context | `this.#logger.error('Error', error, () => ({ id }))` |
| Component context | `providers: [provideLoggerContext({ feature: 'x' })]` |
## Configuration
```typescript
// app.config.ts
import { provideLogging, withLogLevel, withSink, withContext,
LogLevel, ConsoleLogSink } from '@isa/core/logging';
export const appConfig: ApplicationConfig = {
providers: [
provideLogging(
withLogLevel(isDevMode() ? LogLevel.Debug : LogLevel.Warn),
withSink(ConsoleLogSink),
withContext({ app: 'ISA', version: '1.0.0' })
)
]
};
```
## Log Levels
| Level | Use Case | Example |
|-------|----------|---------|
| `Trace` | Method entry/exit | `this.#logger.trace('Entering processData')` |
| `Debug` | Development info | `this.#logger.debug('Variable state', () => ({ x }))` |
| `Info` | Runtime events | `this.#logger.info('User logged in', { userId })` |
| `Warn` | Warnings | `this.#logger.warn('Deprecated API used')` |
| `Error` | Errors | `this.#logger.error('Operation failed', error)` |
| `Off` | Disable logging | `withLogLevel(LogLevel.Off)` |
## Decision Trees
### Context Type Decision
```
Value changes at runtime?
├─ Yes → () => ({ value: this.getValue() })
└─ No → { value: 'static' }
Computing value is expensive?
├─ Yes → () => ({ data: this.compute() })
└─ No → Either works
```
### Log Level Decision
```
Method flow details? → Trace
Development debug? → Debug
Runtime information? → Info
Potential problem? → Warn
Error occurred? → Error
```
## Performance Tips
```typescript
// ✅ DO: Lazy evaluation
this.#logger.debug('Data', () => ({
result: this.expensive() // Only runs if debug enabled
}));
// ❌ DON'T: Eager evaluation
this.#logger.debug('Data', {
result: this.expensive() // Always runs
});
// ✅ DO: Log aggregates
this.#logger.info('Batch done', () => ({ count: items.length }));
// ❌ DON'T: Log in loops
for (const item of items) {
this.#logger.debug('Item', { item }); // Performance hit
}
```
## Testing
```typescript
import { createComponentFactory, Spectator } from '@ngneat/spectator/jest';
import { LoggingService } from '@isa/core/logging';
describe('MyComponent', () => {
const createComponent = createComponentFactory({
component: MyComponent,
mocks: [LoggingService]
});
it('logs error', () => {
const spectator = createComponent();
const logger = spectator.inject(LoggingService);
spectator.component.operation();
expect(logger.error).toHaveBeenCalled();
});
});
```
## Custom Sink
```typescript
import { Injectable } from '@angular/core';
import { Sink, LogLevel, LoggerContext } from '@isa/core/logging';
@Injectable()
export class CustomSink implements Sink {
log(level: LogLevel, message: string, context?: LoggerContext, error?: Error): void {
// Implementation
}
}
// Register
provideLogging(withSink(CustomSink))
```
## Sink Function (with DI)
```typescript
import { inject } from '@angular/core';
import { SinkFn, LogLevel } from '@isa/core/logging';
export const remoteSink: SinkFn = () => {
const http = inject(HttpClient);
return (level, message, context, error) => {
if (level === LogLevel.Error) {
http.post('/api/logs', { level, message, context, error }).subscribe();
}
};
};
// Register
provideLogging(withSinkFn(remoteSink))
```
## Common Imports
```typescript
// Main imports
import { logger, provideLoggerContext } from '@isa/core/logging';
// Configuration imports
import {
provideLogging,
withLogLevel,
withSink,
withContext,
LogLevel,
ConsoleLogSink
} from '@isa/core/logging';
// Type imports
import {
LoggerApi,
Sink,
SinkFn,
LoggerContext
} from '@isa/core/logging';
```

View File

@@ -0,0 +1,235 @@
# Logging Troubleshooting
## 1. Logs Not Appearing
**Problem:** Logger called but nothing in console.
**Solutions:**
```typescript
// Check log level
provideLogging(
withLogLevel(isDevMode() ? LogLevel.Debug : LogLevel.Warn)
)
// Add sink
provideLogging(
withLogLevel(LogLevel.Debug),
withSink(ConsoleLogSink) // Required!
)
// Verify configuration in app.config.ts
export const appConfig: ApplicationConfig = {
providers: [
provideLogging(...) // Must be present
]
};
```
## 2. NullInjectorError
**Error:** `NullInjectorError: No provider for LoggingService!`
**Solution:**
```typescript
// app.config.ts
import { provideLogging, withLogLevel, withSink,
LogLevel, ConsoleLogSink } from '@isa/core/logging';
export const appConfig: ApplicationConfig = {
providers: [
provideLogging(
withLogLevel(LogLevel.Debug),
withSink(ConsoleLogSink)
)
]
};
```
## 3. Context Not Showing
**Problem:** Context passed but doesn't appear.
**Check:**
```typescript
// ✅ Both work:
this.#logger.info('Message', () => ({ id: '123' })); // Function
this.#logger.info('Message', { id: '123' }); // Object
// ❌ Common mistake:
const ctx = { id: '123' };
this.#logger.info('Message', ctx); // Actually works!
// Verify hierarchical merge:
// Global → Component → Instance → Message
```
## 4. Performance Issues
**Problem:** Slow when debug logging enabled.
**Solutions:**
```typescript
// ✅ Use lazy evaluation
this.#logger.debug('Data', () => ({
expensive: this.compute() // Only if debug enabled
}));
// ✅ Reduce log frequency
this.#logger.debug('Batch', () => ({
count: items.length // Not each item
}));
// ✅ Increase production level
provideLogging(
withLogLevel(isDevMode() ? LogLevel.Debug : LogLevel.Warn)
)
```
## 5. Error Object Not Logged
**Problem:** Error shows as `[object Object]`.
**Solution:**
```typescript
// ❌ Wrong
this.#logger.error('Failed', { error }); // Don't wrap in object
// ✅ Correct
this.#logger.error('Failed', error as Error, () => ({
additionalContext: 'value'
}));
```
## 6. TypeScript Errors
**Error:** `Type 'X' is not assignable to 'MaybeLoggerContextFn'`
**Solution:**
```typescript
// ❌ Wrong type
this.#logger.info('Message', 'string'); // Invalid
// ✅ Correct types
this.#logger.info('Message', { key: 'value' });
this.#logger.info('Message', () => ({ key: 'value' }));
```
## 7. Logs in Tests
**Problem:** Test output cluttered with logs.
**Solutions:**
```typescript
// Mock logging service
import { createComponentFactory, Spectator } from '@ngneat/spectator/jest';
import { LoggingService } from '@isa/core/logging';
const createComponent = createComponentFactory({
component: MyComponent,
mocks: [LoggingService] // Mocks all log methods
});
// Or disable in tests
TestBed.configureTestingModule({
providers: [
provideLogging(withLogLevel(LogLevel.Off))
]
});
```
## 8. Undefined Property Error
**Error:** `Cannot read property 'X' of undefined`
**Problem:** Accessing uninitialized property in logger context.
**Solutions:**
```typescript
// ❌ Problem
#logger = logger(() => ({
userId: this.userService.currentUserId // May be undefined
}));
// ✅ Solution 1: Optional chaining
#logger = logger(() => ({
userId: this.userService?.currentUserId ?? 'unknown'
}));
// ✅ Solution 2: Delay access
ngOnInit() {
this.#logger.info('Init', () => ({
userId: this.userService.currentUserId // Safe here
}));
}
```
## 9. Circular Dependency
**Error:** `NG0200: Circular dependency in DI detected`
**Cause:** Service A ← → Service B both inject LoggingService.
**Solution:**
```typescript
// ❌ Creates circular dependency
constructor(private loggingService: LoggingService) {}
// ✅ Use factory (no circular dependency)
#logger = logger({ service: 'MyService' });
```
## 10. Custom Sink Not Working
**Problem:** Sink registered but never called.
**Solutions:**
```typescript
// ✅ Correct registration
provideLogging(
withSink(MySink) // Add to config
)
// ✅ Correct signature
export class MySink implements Sink {
log(
level: LogLevel,
message: string,
context?: LoggerContext,
error?: Error
): void {
// Implementation
}
}
// ✅ Sink function must return function
export const mySinkFn: SinkFn = () => {
const http = inject(HttpClient);
return (level, message, context, error) => {
// Implementation
};
};
```
## Quick Diagnostics
```typescript
// Enable all logs temporarily
provideLogging(withLogLevel(LogLevel.Trace))
// Check imports
import { logger } from '@isa/core/logging'; // ✅ Correct
import { logger } from '@isa/core/logging/src/lib/logger.factory'; // ❌ Wrong
// Verify console filters in browser DevTools
// Ensure Info, Debug, Warnings are enabled
```
## Common Error Messages
| Error | Cause | Fix |
|-------|-------|-----|
| `NullInjectorError: LoggingService` | Missing config | Add `provideLogging()` |
| `Type 'X' not assignable` | Wrong context type | Use object or function |
| `Cannot read property 'X'` | Undefined property | Use optional chaining |
| `Circular dependency` | Service injection | Use `logger()` factory |
| Stack overflow | Infinite loop in context | Don't call logger in context |

View File

@@ -0,0 +1,287 @@
---
name: ngrx-resource-api
description: This skill should be used when implementing Angular's Resource API with NgRx Signal Store for reactive data management. Use when creating signal stores that load data reactively, need automatic race condition prevention, or require declarative resource management without RxJS. Applies to data-access libraries, feature stores with API integration, and components needing reactive filtering or pagination.
---
# NgRx Resource API
## Overview
This skill enables integration of Angular's Resource API with NgRx Signal Store to create reactive data flows without RxJS while automatically preventing race conditions. The Resource API handles concurrent request management declaratively, eliminating manual `switchMap` or `takeUntilDestroyed` patterns.
## Core Architectural Concepts
### Reactive Flow Graph
Establish three clear interaction points in the store:
1. **Filter signals trigger resource loading** - Parameter changes automatically reload resources
2. **Methods explicitly invoke operations** - Use `signalMethod` for user-triggered actions
3. **Computed signals derive view models** - Transform loaded data for component consumption
### The withProps Pattern for Dependency Injection
Inject services via `withProps` with underscore-prefixed properties to mark them as internal implementation details:
```typescript
withProps(() => ({
_dataService: inject(DataService),
_notificationService: inject(ToastService),
}))
```
**Benefits:**
- Centralizes dependency injection in one location
- Clear distinction between internal (prefixed) and public properties
- Services available to all subsequent feature sections
## Implementation Steps
### Step 1: Inject Services with withProps
Create the initial `withProps` section to inject required services:
```typescript
export const MyStore = signalStore(
withProps(() => ({
_dataService: inject(DataService),
_toastService: inject(ToastService),
})),
// ... additional features
);
```
**Naming convention:** Prefix all injected services with underscore (`_`) to indicate internal use.
### Step 2: Define Filter State
Add state properties that will serve as resource parameters:
```typescript
withState({
filter: {
searchTerm: '',
category: '',
} as MyFilter,
})
```
### Step 3: Configure Resources
In a subsequent `withProps` section, create resources that reference the injected services and state:
```typescript
withProps((store) => ({
_itemsResource: resource({
params: store.filter,
loader: (loaderParams) => {
const filter = loaderParams.params;
const abortSignal = loaderParams.abortSignal;
return store._dataService.loadItems(filter, abortSignal);
}
})
}))
```
**Key points:**
- Resources automatically reload when `params` signal changes
- `abortSignal` enables automatic cancellation of in-flight requests
- Loader must return a Promise (use `.findPromise()` if service returns Observable)
### Step 4: Expose Read-Only Resources (Optional)
If the resource should be accessible to consumers, expose it as read-only:
```typescript
withProps((store) => ({
itemsResource: store._itemsResource.asReadonly(),
}))
```
**Pattern:** Internal resources use underscore prefix, public versions are read-only without prefix.
### Step 5: Create Signal Methods for Updates
Use `signalMethod` for actions that update state and trigger resource reloads:
```typescript
withMethods((store) => ({
updateFilter: signalMethod<MyFilter>((filter) => {
patchState(store, { filter });
}),
refresh: () => {
store._itemsResource.reload();
}
}))
```
**Important:** `signalMethod` implementations are **untracked by convention** - they don't re-execute when signals change. This provides explicit control flow.
### Step 6: Add Error Handling
Use `withHooks` to react to resource errors:
```typescript
withHooks({
onInit: (store) => {
effect(() => {
const error = store._itemsResource.error();
if (error) {
store._toastService.show('Error: ' + getMessage(error));
}
});
}
})
```
**Pattern:** Error effects should be read-only - they observe errors and trigger side effects, but don't modify state.
## Common Patterns
### Template Integration with linkedSignal
For two-way form binding that synchronizes with the store:
```typescript
export class MyComponent {
#store = inject(MyStore);
// Create linked signal for form field
searchTerm = linkedSignal(() => this.#store.filter().searchTerm);
// Combine form fields into filter object
#linkedFilter = computed(() => ({
searchTerm: this.searchTerm(),
// ... other fields
}));
constructor() {
// Sync form changes back to store
this.#store.updateFilter(this.#linkedFilter);
}
}
```
**Benefits:**
- Two-way binding for forms
- Automatic store synchronization
- Type-safe filter construction
### Working with Resource Data
Access resource data through resource signals:
```typescript
withComputed((store) => ({
items: computed(() => store._itemsResource.value() ?? []),
isLoading: computed(() => store._itemsResource.isLoading()),
hasError: computed(() => store._itemsResource.hasError()),
}))
```
**Available signals:**
- `value()` - The loaded data (undefined while loading)
- `isLoading()` - Loading state boolean
- `hasError()` - Error state boolean
- `error()` - Error object if present
- `status()` - Overall status: 'idle' | 'loading' | 'resolved' | 'error'
### Updating Resource Data Locally
For temporary working copies before server writes:
```typescript
withMethods((store) => ({
updateLocalItem: (id: string, changes: Partial<Item>) => {
store._itemsResource.update((currentItems) => {
return currentItems.map(item =>
item.id === id ? { ...item, ...changes } : item
);
});
}
}))
```
**Note:** This pattern feels unconventional but aligns with maintaining temporary working copies before server persistence.
### Multiple Resources in One Store
Combine multiple resources for complex data requirements:
```typescript
withProps((store) => ({
_itemsResource: resource({
params: store.filter,
loader: (params) => store._dataService.loadItems(params.params, params.abortSignal)
}),
_detailsResource: resource({
params: store.selectedId,
loader: (params) => {
if (!params.params) return Promise.resolve(null);
return store._dataService.loadDetails(params.params, params.abortSignal);
}
})
}))
```
**Pattern:** Each resource has independent params and loading state, but can share service instances.
## Important Considerations
### Race Condition Prevention
The Resource API automatically handles race conditions:
- New requests automatically cancel pending requests
- No need for `switchMap`, `takeUntilDestroyed`, or manual abort handling
- Declarative parameter changes trigger clean cancellation
### Untracked Signal Methods
`signalMethod` implementations deliberately skip reactive tracking:
- Provides explicit, predictable control flow
- Prevents unexpected re-executions from signal changes
- Makes side effects obvious at call sites
### Loader Function Requirements
Loaders must:
- Return a `Promise` (not Observable)
- Accept and pass through the `abortSignal` to enable cancellation
- Handle the signal in the underlying HTTP call
**Converting Observables:**
```typescript
loader: (params) => {
return firstValueFrom(
this._service.load$(params.params)
.pipe(takeUntilDestroyed(this._destroyRef))
);
}
```
### Resource Lifecycle
Resources maintain their own state machine:
1. **Idle** - Initial state before first load
2. **Loading** - Request in progress
3. **Resolved** - Data loaded successfully
4. **Error** - Request failed
State transitions automatically trigger reactive updates to dependent computeds and effects.
## When to Use This Pattern
**Use Resource API with Signal Store when:**
- Loading data based on reactive filter/search parameters
- Need automatic race condition handling for concurrent requests
- Want declarative data loading without RxJS subscriptions
- Building stores with frequently changing query parameters
- Implementing pagination, filtering, or search features
**Consider alternatives when:**
- Simple one-time data loads (use `rxMethod` or direct service calls)
- Complex Observable chains with multiple operators needed
- Need fine-grained control over request timing/caching
- Working with WebSocket or SSE streams (use `rxMethod` instead)

View File

@@ -0,0 +1,333 @@
---
name: tailwind
description: This skill should be used when working with Tailwind CSS styling in the ISA-Frontend project. Use it when writing component styles, choosing color values, applying typography, creating buttons, or determining appropriate spacing and layout utilities. Essential for maintaining design system consistency.
---
# ISA Tailwind Design System
## Overview
Assist with applying the ISA-specific Tailwind CSS design system throughout the ISA-Frontend Angular monorepo. This skill provides comprehensive knowledge of custom utilities, color palettes, typography classes, button variants, and layout patterns specific to this project.
## When to Use This Skill
Invoke this skill when:
- **After** checking `libs/ui/**` for existing components (always check first!)
- Styling layout and spacing for components
- Choosing appropriate color values for custom elements
- Applying typography classes to text content
- Determining spacing, layout, or responsive breakpoints
- Customizing or extending existing UI components
- Ensuring design system consistency
- Questions about which Tailwind utility classes are available
**Important**: This skill provides Tailwind utilities. Always prefer using components from `@isa/ui/*` libraries before applying custom Tailwind styles.
**Works together with:**
- **[angular-template](../angular-template/SKILL.md)** - Angular template syntax, control flow (@if, @for, @defer), and binding patterns
- **[html-template](../html-template/SKILL.md)** - E2E testing attributes (`data-what`, `data-which`) and ARIA accessibility
When building Angular components, these three skills work together:
1. Use **angular-template** for Angular syntax and control flow
2. Use **html-template** for `data-*` and ARIA attributes
3. Use **tailwind** (this skill) for styling with the ISA design system
## Core Design System Principles
### 0. Component Libraries First (Most Important)
**Always check `libs/ui/**` for existing components before writing custom Tailwind styles.**
The project has 17 specialized UI component libraries:
- `@isa/ui/buttons` - Button components
- `@isa/ui/dialogs` - Dialog/modal components
- `@isa/ui/inputs` - Input field components
- `@isa/ui/forms` - Form components
- `@isa/ui/cards` - Card components
- `@isa/ui/layout` - Layout components (including breakpoint service)
- `@isa/ui/tables` - Table components
- And 10+ more specialized libraries
**Workflow**:
1. First, search for existing components in `libs/ui/**` that match your needs
2. If found, import and use the component (prefer composition over custom styling)
3. Only use Tailwind utilities for:
- Layout/spacing adjustments
- Component-specific customizations
- Cases where no suitable UI component exists
**Example**:
```typescript
// ✅ Correct - Use existing component
import { ButtonComponent } from '@isa/ui/buttons';
// ❌ Wrong - Don't recreate with Tailwind
<button class="btn btn-accent-1">...</button>
```
### 1. ISA-Prefixed Colors Only
**Always use `isa-*` prefixed color utilities.** Other color names exist only for backwards compatibility and should not be used in new code.
**Correct color usage**:
- `bg-isa-accent-red`, `bg-isa-accent-blue`, `bg-isa-accent-green`
- `bg-isa-secondary-100` through `bg-isa-secondary-900`
- `bg-isa-neutral-100` through `bg-isa-neutral-900`
- `text-isa-white`, `text-isa-black`
**Example**:
```html
<!-- ✅ Correct -->
<div class="bg-isa-accent-red text-isa-white">Error message</div>
<button class="bg-isa-secondary-600 hover:bg-isa-secondary-700">Action</button>
<!-- ❌ Wrong - deprecated colors -->
<div class="bg-accent-1 text-accent-1-content">...</div>
<div class="bg-brand">...</div>
```
### 2. ISA-Prefixed Typography
Always use ISA typography classes instead of arbitrary font sizes:
- **Headings**: `.isa-text-heading-1-bold`, `.isa-text-heading-2-bold`, `.isa-text-heading-3-bold`
- **Subtitles**: `.isa-text-subtitle-1-bold`, `.isa-text-subtitle-2-bold`
- **Body**: `.isa-text-body-1-regular`, `.isa-text-body-1-bold`, `.isa-text-body-2-regular`, `.isa-text-body-2-bold`
- **Captions**: `.isa-text-caption-regular`, `.isa-text-caption-bold`, `.isa-text-caption-caps`
### 3. Responsive Design with Breakpoint Service
Prefer the breakpoint service from `@isa/ui/layout` for reactive breakpoint detection:
```typescript
import { breakpoint, Breakpoint } from '@isa/ui/layout';
// In component
isDesktop = breakpoint([Breakpoint.Desktop, Breakpoint.DekstopL, Breakpoint.DekstopXL]);
```
```html
@if (isDesktop()) {
<div class="desktop-layout">...</div>
}
```
Only use Tailwind breakpoint utilities (`isa-desktop:`, `isa-desktop-l:`, `isa-desktop-xl:`) when the breakpoint service is not appropriate (e.g., pure CSS solutions).
## Quick Reference
### Typography Selection Guide
**Headings**:
- Large hero text: `.isa-text-heading-1-bold` (60px)
- Section headers: `.isa-text-heading-2-bold` (48px)
- Subsection headers: `.isa-text-heading-3-bold` (40px)
**Subtitles**:
- Prominent subtitles: `.isa-text-subtitle-1-bold` (28px)
- Section labels: `.isa-text-subtitle-2-bold` (16px, uppercase)
**Body Text**:
- Standard text: `.isa-text-body-1-regular` (16px)
- Emphasized text: `.isa-text-body-1-bold` (16px)
- Smaller text: `.isa-text-body-2-regular` (14px)
- Smaller emphasized: `.isa-text-body-2-bold` (14px)
**Captions**:
- Small labels: `.isa-text-caption-regular` (12px)
- Small emphasized: `.isa-text-caption-bold` (12px)
- Uppercase labels: `.isa-text-caption-caps` (12px, uppercase)
Each variant has `-big` and `-xl` responsive sizes for larger breakpoints.
### Color Selection Guide
**Always use `isa-*` prefixed colors. Other colors are deprecated.**
**Status/Accent Colors**:
- Success/Confirm: `bg-isa-accent-green`
- Error/Danger: `bg-isa-accent-red`
- Primary/Info: `bg-isa-accent-blue`
**Brand Secondary Colors** (100 = lightest, 900 = darkest):
- Very light: `bg-isa-secondary-100`, `bg-isa-secondary-200`
- Light: `bg-isa-secondary-300`, `bg-isa-secondary-400`
- Medium: `bg-isa-secondary-500`, `bg-isa-secondary-600`
- Dark: `bg-isa-secondary-700`, `bg-isa-secondary-800`
- Very dark: `bg-isa-secondary-900`
**Neutral UI** (100 = lightest, 900 = darkest):
- Light backgrounds: `bg-isa-neutral-100`, `bg-isa-neutral-200`, `bg-isa-neutral-300`
- Medium backgrounds: `bg-isa-neutral-400`, `bg-isa-neutral-500`, `bg-isa-neutral-600`
- Dark backgrounds/text: `bg-isa-neutral-700`, `bg-isa-neutral-800`, `bg-isa-neutral-900`
**Basic Colors**:
- White: `bg-isa-white`, `text-isa-white`
- Black: `bg-isa-black`, `text-isa-black`
**Example Usage**:
```html
<!-- Status indicators -->
<div class="bg-isa-accent-green text-isa-white">Success</div>
<div class="bg-isa-accent-red text-isa-white">Error</div>
<!-- Backgrounds -->
<div class="bg-isa-neutral-100">Light surface</div>
<div class="bg-isa-secondary-600 text-isa-white">Brand element</div>
```
### Spacing Patterns
**Component Padding**:
- Cards: `p-card` (20px) or `p-5` (1.25rem)
- General spacing: `p-4` (1rem), `p-6` (1.5rem), `p-8` (2rem)
- Tight spacing: `p-2` (0.5rem), `p-3` (0.75rem)
**Gap/Grid Spacing**:
- Tight spacing: `gap-2` (0.5rem), `gap-3` (0.75rem)
- Medium spacing: `gap-4` (1rem), `gap-6` (1.5rem)
- Wide spacing: `gap-8` (2rem), `gap-10` (2.5rem)
- Split screen: `gap-split-screen`
**Note**: Prefer Tailwind's standard rem-based spacing (e.g., `p-4`, `gap-6`) over pixel-based utilities (`px-*`) for better scalability and accessibility.
**Layout Heights**:
- Split screen tablet: `h-split-screen-tablet`
- Split screen desktop: `h-split-screen-desktop`
### Z-Index Layering
Apply semantic z-index values for proper layering:
- Dropdowns: `z-dropdown` (50)
- Sticky elements: `z-sticky` (100)
- Fixed elements: `z-fixed` (150)
- Modal backdrops: `z-modalBackdrop` (200)
- Modals: `z-modal` (250)
- Popovers: `z-popover` (300)
- Tooltips: `z-tooltip` (350)
## Common Styling Patterns
**Important**: These are examples for when UI components don't exist. Always check `@isa/ui/*` libraries first!
### Layout Spacing (Use Tailwind)
```html
<!-- Container with padding -->
<div class="p-6">
<h2 class="isa-text-heading-2-bold mb-4">Section Title</h2>
<div class="flex flex-col gap-4">
<!-- Content items -->
</div>
</div>
```
### Grid Layout (Use Tailwind)
```html
<!-- Responsive grid with gap -->
<div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
<!-- Grid items -->
</div>
```
### Card Layout (Prefer @isa/ui/cards if available)
```html
<div class="bg-isa-white p-5 rounded shadow-card">
<h3 class="isa-text-subtitle-1-bold mb-4">Card Title</h3>
<p class="isa-text-body-1-regular">Card content...</p>
</div>
```
### Form Group (Prefer @isa/ui/forms if available)
```html
<div class="flex flex-col gap-2">
<label class="isa-text-body-2-semibold text-isa-black">Field Label</label>
<!-- Use component from @isa/ui/inputs if available -->
<input class="shadow-input rounded border border-isa-neutral-400 p-2.5" />
</div>
```
### Button Group (Use @isa/ui/buttons)
```typescript
// ✅ Preferred - Use component library
import { ButtonComponent } from '@isa/ui/buttons';
```
```html
<div class="flex gap-4">
<!-- Use actual button components from @isa/ui/buttons -->
<isa-button variant="primary">Save</isa-button>
<isa-button variant="secondary">Cancel</isa-button>
</div>
```
### Split Screen Layout (Use Tailwind)
```html
<div class="grid grid-cols-split-screen gap-split-screen h-split-screen-desktop">
<aside class="bg-isa-neutral-100 p-5">Sidebar</aside>
<main class="bg-isa-white p-8">Content</main>
</div>
```
## Resources
### references/design-system.md
Comprehensive reference documentation containing:
- Complete color palette with hex values
- All typography class specifications
- Button plugin CSS custom properties
- Spacing and layout utilities
- Border radius, shadows, and z-index values
- Custom variants and best practices
Load this reference when:
- Looking up specific hex color values
- Determining exact typography specifications
- Understanding button CSS custom properties
- Finding less common utility classes
- Verifying available shadow or radius utilities
## Best Practices
1. **Component libraries first**: Always check `libs/ui/**` before writing custom Tailwind styles
2. **ISA-prefixed colors only**: Always use `isa-*` colors (e.g., `bg-isa-accent-red`, `text-isa-neutral-700`)
3. **Use rem over px**: Prefer Tailwind's default rem-based spacing (e.g., `p-4`, `gap-6`) over pixel-based utilities
4. **Typography system**: Never use arbitrary font sizes - always use `.isa-text-*` classes
5. **Breakpoints**: Use breakpoint service from `@isa/ui/layout` for logic
6. **Z-index**: Always use semantic z-index utilities, never arbitrary values
7. **Consistency**: Always use design system utilities instead of arbitrary values
## Anti-Patterns to Avoid
❌ **Don't** use deprecated colors (backwards compatibility only):
```html
<div class="bg-accent-1">...</div> <!-- Wrong - deprecated -->
<div class="bg-brand">...</div> <!-- Wrong - deprecated -->
<div class="bg-surface">...</div> <!-- Wrong - deprecated -->
<div class="bg-isa-secondary-600">...</div> <!-- Correct -->
```
❌ **Don't** use arbitrary values when utilities exist:
```html
<p class="text-[16px]">Text</p> <!-- Wrong -->
<p class="isa-text-body-1-regular">Text</p> <!-- Correct -->
```
❌ **Don't** hardcode hex colors:
```html
<div class="bg-[#DF001B]">...</div> <!-- Wrong -->
<div class="bg-isa-accent-red">...</div> <!-- Correct -->
```
❌ **Don't** recreate components with Tailwind:
```html
<button class="btn btn-accent-1">...</button> <!-- Wrong - use @isa/ui/buttons -->
<isa-button variant="primary">...</isa-button> <!-- Correct -->
```
❌ **Don't** use arbitrary z-index:
```html
<div class="z-[999]">...</div> <!-- Wrong -->
<div class="z-modal">...</div> <!-- Correct -->
```
**Do** leverage the component libraries and ISA design system for consistency and maintainability.

View File

@@ -0,0 +1,173 @@
# ISA Tailwind Design System Reference
This document provides a comprehensive reference for the ISA-specific Tailwind CSS design system used throughout the ISA-Frontend project.
## Custom Breakpoints
### ISA Breakpoints (Preferred)
- `isa-desktop`: 1024px
- `isa-desktop-l`: 1440px
- `isa-desktop-xl`: 1920px
**Note**: Prefer using the breakpoint service from `@isa/ui/layout` for reactive breakpoint detection instead of CSS-only solutions.
## Z-Index System
Predefined z-index values for consistent layering:
- `z-dropdown`: 50
- `z-sticky`: 100
- `z-fixed`: 150
- `z-modalBackdrop`: 200
- `z-modal`: 250
- `z-popover`: 300
- `z-tooltip`: 350
**Usage**: `z-modal`, `z-tooltip`, etc.
## Color Palette
**IMPORTANT: Only use `isa-*` prefixed colors in new code.** Other colors listed below exist only for backwards compatibility and should NOT be used.
### ISA Brand Colors (Use These)
#### Accent Colors
- `isa-accent-red`: #DF001B
- `isa-accent-blue`: #354ACB
- `isa-accent-green`: #26830C
#### Accent Color Shades
- `isa-shades-red-600`: #C60018
- `isa-shades-red-700`: #B30016
#### Secondary Colors (100-900 scale)
- `isa-secondary-100`: #EBEFFF (lightest)
- `isa-secondary-200`: #B9C4FF
- `isa-secondary-300`: #8FA0FF
- `isa-secondary-400`: #6E82FE
- `isa-secondary-500`: #556AEB
- `isa-secondary-600`: #354ACB
- `isa-secondary-700`: #1D2F99
- `isa-secondary-800`: #0C1A66
- `isa-secondary-900`: #020A33 (darkest)
#### Neutral Colors (100-900 scale)
- `isa-neutral-100`: #F8F9FA (lightest)
- `isa-neutral-200`: #E9ECEF
- `isa-neutral-300`: #DEE2E6
- `isa-neutral-400`: #CED4DA
- `isa-neutral-500`: #A5ACB4
- `isa-neutral-600`: #6C757D
- `isa-neutral-700`: #495057
- `isa-neutral-800`: #343A40
- `isa-neutral-900`: #212529 (darkest)
#### Basic Colors
- `isa-black`: #000000
- `isa-white`: #FFFFFF
**Usage**: `bg-isa-accent-red`, `text-isa-secondary-600`, `border-isa-neutral-400`
### Deprecated Colors (DO NOT USE - Backwards Compatibility Only)
The following colors exist in the codebase for backwards compatibility. **DO NOT use them in new code.**
#### Deprecated Semantic Colors
- `background`, `background-content`
- `surface`, `surface-content`, `surface-2`, `surface-2-content`
- `components-menu`, `components-menu-content`, `components-menu-seperator`, `components-menu-hover`
- `components-button`, `components-button-content`, `components-button-light`, `components-button-hover`
- `accent-1`, `accent-1-content`, `accent-1-hover`, `accent-1-active`
- `accent-2`, `accent-2-content`, `accent-2-hover`, `accent-2-active`
#### Deprecated Named Colors
- `warning`, `brand`
- `customer`, `font-customer`, `active-customer`, `inactive-customer`, `disabled-customer`
- `branch`, `font-branch`, `active-branch`, `inactive-branch`, `disabled-branch`
- `accent-teal`, `accent-green`, `accent-orange`, `accent-darkblue`
- `ucla-blue`, `wild-blue-yonder`, `dark-cerulean`, `cool-grey`
- `glitter`, `munsell`, `onyx`, `dark-goldenrod`, `cadet`, `cadet-blue`
- `control-border`, `background-liste`
**These colors should NOT be used in new code. Use `isa-*` prefixed colors instead.**
## Typography
### ISA Typography Utilities
All typography utilities use **Open Sans** font family.
#### Headings
**Heading 1 Bold** (`.isa-text-heading-1-bold`):
- Size: 3.75rem (60px)
- Weight: 700
- Line Height: 4.5rem (72px)
- Letter Spacing: 0.02813rem
**Heading 2 Bold** (`.isa-text-heading-2-bold`):
- Size: 3rem (48px)
- Weight: 700
- Line Height: 4rem (64px)
**Heading 3 Bold** (`.isa-text-heading-3-bold`):
- Size: 2.5rem (40px)
- Weight: 700
- Line Height: 3rem (48px)
#### Subtitles
**Subtitle 1 Regular** (`.isa-text-subtitle-1-regular`):
- Size: 1.75rem (28px)
- Weight: 400
- Line Height: 2.5rem (40px)
**Subtitle 1 Bold** (`.isa-text-subtitle-1-bold`):
- Size: 1.75rem (28px)
- Weight: 700
- Line Height: 2.5rem (40px)
**Subtitle 2 Bold** (`.isa-text-subtitle-2-bold`):
- Size: 1rem (16px)
- Weight: 700
- Line Height: 1.5rem (24px)
- Letter Spacing: 0.025rem
- Text Transform: UPPERCASE
#### Body Text
**Body 1 Variants** (1rem / 16px base):
- `.isa-text-body-1-bold`: Weight 700, Line Height 1.5rem
- `.isa-text-body-1-bold-big`: Size 1.25rem, Weight 700, Line Height 1.75rem
- `.isa-text-body-1-bold-xl`: Size 1.375rem, Weight 700, Line Height 2.125rem
- `.isa-text-body-1-semibold`: Weight 600, Line Height 1.5rem
- `.isa-text-body-1-regular`: Weight 400, Line Height 1.5rem
- `.isa-text-body-1-regular-big`: Size 1.25rem, Weight 400, Line Height 1.75rem
- `.isa-text-body-1-regular-xl`: Size 1.375rem, Weight 400, Line Height 2.125rem
**Body 2 Variants** (0.875rem / 14px base):
- `.isa-text-body-2-bold`: Weight 700, Line Height 1.25rem
- `.isa-text-body-2-bold-big`: Size 1.125rem, Weight 700, Line Height 1.625rem
- `.isa-text-body-2-bold-xl`: Size 1.25rem, Weight 700, Line Height 1.75rem
- `.isa-text-body-2-semibold`: Weight 600, Line Height 1.25rem
- `.isa-text-body-2-regular`: Weight 400, Line Height 1.25rem
- `.isa-text-body-2-regular-big`: Size 1.125rem, Weight 400, Line Height 1.625rem
- `.isa-text-body-2-regular-xl`: Size 1.125rem, Weight 400, Line Height 1.75rem
#### Caption Text
**Caption Variants** (0.75rem / 12px base):
- `.isa-text-caption-bold`: Weight 700, Line Height 1rem
- `.isa-text-caption-bold-big`: Size 0.875rem, Weight 700, Line Height 1.25rem
- `.isa-text-caption-bold-xl`: Size 0.875rem, Weight 700, Line Height 1.25rem
- `.isa-text-caption-caps`: Weight 700, Line Height 1rem, UPPERCASE
- `.isa-text-caption-regular`: Weight 400, Line Height 1rem
- `.isa-text-caption-regular-big`: Size 0.875rem, Weight 400, Line Height 1.25rem
- `.isa-text-caption-regular-xl`: Size 0.875rem, Weight 400, Line Height 1.25rem
## Best Practices
1. **Use ISA-prefixed utilities**: Prefer `isa-text-*`, `isa-accent-*`, etc. for consistency
2. **Follow typography system**: Use the predefined typography classes instead of custom font sizes
3. **Use breakpoint service**: Import from `@isa/ui/layout` for reactive breakpoint detection
5. **Z-index system**: Always use predefined z-index utilities for layering

View File

@@ -0,0 +1,346 @@
# Jest to Vitest Migration Patterns
## Overview
This reference provides syntax mappings and patterns for migrating tests from Jest (with Spectator) to Vitest (with Angular Testing Library).
## Configuration Migration
### Jest Config → Vitest Config
**Before (jest.config.ts):**
```typescript
export default {
displayName: 'my-lib',
preset: '../../jest.preset.js',
setupFilesAfterEnv: ['<rootDir>/src/test-setup.ts'],
coverageDirectory: '../../coverage/libs/my-lib',
transform: {
'^.+\\.(ts|mjs|js|html)$': 'jest-preset-angular',
},
transformIgnorePatterns: ['node_modules/(?!.*\\.mjs$)'],
snapshotSerializers: [
'jest-preset-angular/build/serializers/no-ng-attributes',
'jest-preset-angular/build/serializers/ng-snapshot',
],
};
```
**After (vitest.config.ts):**
```typescript
import { defineConfig } from 'vitest/config';
import angular from '@analogjs/vite-plugin-angular';
export default defineConfig({
plugins: [angular()],
test: {
globals: true,
environment: 'jsdom',
setupFiles: ['src/test-setup.ts'],
include: ['**/*.spec.ts'],
reporters: ['default'],
coverage: {
provider: 'v8',
reporter: ['text', 'json', 'html'],
},
},
});
```
### Test Setup Migration
**Before (test-setup.ts - Jest):**
```typescript
import 'jest-preset-angular/setup-jest';
```
**After (test-setup.ts - Vitest):**
```typescript
import '@analogjs/vitest-angular/setup-zone';
```
## Import Changes
### Test Function Imports
**Before (Jest):**
```typescript
import { describe, it, expect, beforeEach, afterEach } from '@jest/globals';
```
**After (Vitest):**
```typescript
import { describe, it, expect, beforeEach, afterEach, vi } from 'vitest';
```
### Mock Imports
**Before (Jest):**
```typescript
jest.fn()
jest.spyOn()
jest.mock()
jest.useFakeTimers()
```
**After (Vitest):**
```typescript
vi.fn()
vi.spyOn()
vi.mock()
vi.useFakeTimers()
```
## Mock Migration Patterns
### Function Mocks
**Before (Jest):**
```typescript
const mockFn = jest.fn();
const mockFnWithReturn = jest.fn().mockReturnValue('value');
const mockFnWithAsync = jest.fn().mockResolvedValue('async value');
```
**After (Vitest):**
```typescript
const mockFn = vi.fn();
const mockFnWithReturn = vi.fn().mockReturnValue('value');
const mockFnWithAsync = vi.fn().mockResolvedValue('async value');
```
### Spy Migration
**Before (Jest):**
```typescript
const spy = jest.spyOn(service, 'method');
spy.mockImplementation(() => 'mocked');
```
**After (Vitest):**
```typescript
const spy = vi.spyOn(service, 'method');
spy.mockImplementation(() => 'mocked');
```
### Module Mocks
**Before (Jest):**
```typescript
jest.mock('@isa/core/logging', () => ({
logger: jest.fn(() => ({
info: jest.fn(),
error: jest.fn(),
})),
}));
```
**After (Vitest):**
```typescript
vi.mock('@isa/core/logging', () => ({
logger: vi.fn(() => ({
info: vi.fn(),
error: vi.fn(),
})),
}));
```
## Spectator → Angular Testing Library
### Component Testing
**Before (Spectator):**
```typescript
import { createComponentFactory, Spectator } from '@ngneat/spectator/jest';
describe('MyComponent', () => {
let spectator: Spectator<MyComponent>;
const createComponent = createComponentFactory({
component: MyComponent,
imports: [CommonModule],
providers: [
{ provide: MyService, useValue: mockService },
],
});
beforeEach(() => {
spectator = createComponent();
});
it('should render title', () => {
expect(spectator.query('.title')).toHaveText('Hello');
});
it('should handle click', () => {
spectator.click('.button');
expect(mockService.doSomething).toHaveBeenCalled();
});
});
```
**After (Angular Testing Library):**
```typescript
import { render, screen, fireEvent } from '@testing-library/angular';
describe('MyComponent', () => {
it('should render title', async () => {
await render(MyComponent, {
imports: [CommonModule],
providers: [
{ provide: MyService, useValue: mockService },
],
});
expect(screen.getByText('Hello')).toBeInTheDocument();
});
it('should handle click', async () => {
await render(MyComponent, {
providers: [{ provide: MyService, useValue: mockService }],
});
fireEvent.click(screen.getByRole('button'));
expect(mockService.doSomething).toHaveBeenCalled();
});
});
```
### Query Selectors
| Spectator | Angular Testing Library |
|-----------|------------------------|
| `spectator.query('.class')` | `screen.getByTestId()` or `screen.getByRole()` |
| `spectator.queryAll('.class')` | `screen.getAllByRole()` |
| `spectator.query('button')` | `screen.getByRole('button')` |
| `spectator.query('[data-testid]')` | `screen.getByTestId()` |
### Events
| Spectator | Angular Testing Library |
|-----------|------------------------|
| `spectator.click(element)` | `fireEvent.click(element)` or `await userEvent.click(element)` |
| `spectator.typeInElement(value, element)` | `await userEvent.type(element, value)` |
| `spectator.blur(element)` | `fireEvent.blur(element)` |
| `spectator.focus(element)` | `fireEvent.focus(element)` |
### Service Testing
**Before (Spectator):**
```typescript
import { createServiceFactory, SpectatorService } from '@ngneat/spectator/jest';
describe('MyService', () => {
let spectator: SpectatorService<MyService>;
const createService = createServiceFactory({
service: MyService,
providers: [
{ provide: HttpClient, useValue: mockHttp },
],
});
beforeEach(() => {
spectator = createService();
});
it('should fetch data', () => {
spectator.service.getData().subscribe(data => {
expect(data).toEqual(expectedData);
});
});
});
```
**After (TestBed):**
```typescript
import { TestBed } from '@angular/core/testing';
describe('MyService', () => {
let service: MyService;
beforeEach(() => {
TestBed.configureTestingModule({
providers: [
MyService,
{ provide: HttpClient, useValue: mockHttp },
],
});
service = TestBed.inject(MyService);
});
it('should fetch data', () => {
service.getData().subscribe(data => {
expect(data).toEqual(expectedData);
});
});
});
```
## Async Testing
### Observable Testing
**Before (Jest):**
```typescript
it('should emit values', (done) => {
service.data$.subscribe({
next: (value) => {
expect(value).toBe(expected);
done();
},
});
});
```
**After (Vitest):**
```typescript
import { firstValueFrom } from 'rxjs';
it('should emit values', async () => {
const value = await firstValueFrom(service.data$);
expect(value).toBe(expected);
});
```
### Timer Mocks
**Before (Jest):**
```typescript
jest.useFakeTimers();
service.startTimer();
jest.advanceTimersByTime(1000);
expect(callback).toHaveBeenCalled();
jest.useRealTimers();
```
**After (Vitest):**
```typescript
vi.useFakeTimers();
service.startTimer();
vi.advanceTimersByTime(1000);
expect(callback).toHaveBeenCalled();
vi.useRealTimers();
```
## Common Matchers
| Jest | Vitest |
|------|--------|
| `expect(x).toBe(y)` | Same |
| `expect(x).toEqual(y)` | Same |
| `expect(x).toHaveBeenCalled()` | Same |
| `expect(x).toHaveBeenCalledWith(y)` | Same |
| `expect(x).toMatchSnapshot()` | `expect(x).toMatchSnapshot()` |
| `expect(x).toHaveText('text')` | `expect(x).toHaveTextContent('text')` (with jest-dom) |
## Migration Checklist
1. [ ] Update `vitest.config.ts`
2. [ ] Update `test-setup.ts`
3. [ ] Replace `jest.fn()` with `vi.fn()`
4. [ ] Replace `jest.spyOn()` with `vi.spyOn()`
5. [ ] Replace `jest.mock()` with `vi.mock()`
6. [ ] Replace Spectator with Angular Testing Library
7. [ ] Update queries to use accessible selectors
8. [ ] Update async patterns
9. [ ] Run tests and fix any remaining issues
10. [ ] Remove Jest dependencies from `package.json`

View File

@@ -0,0 +1,293 @@
# Zod Patterns Reference
## Overview
Zod is a TypeScript-first schema validation library. Use it for runtime validation at system boundaries (API responses, form inputs, external data).
## Basic Schema Patterns
### Primitive Types
```typescript
import { z } from 'zod';
// Basic types
const stringSchema = z.string();
const numberSchema = z.number();
const booleanSchema = z.boolean();
const dateSchema = z.date();
// With constraints
const emailSchema = z.string().email();
const positiveNumber = z.number().positive();
const nonEmptyString = z.string().min(1);
const optionalString = z.string().optional();
const nullableString = z.string().nullable();
```
### Object Schemas
```typescript
// Basic object
const userSchema = z.object({
id: z.string().uuid(),
email: z.string().email(),
name: z.string().min(1),
age: z.number().int().positive().optional(),
role: z.enum(['admin', 'user', 'guest']),
createdAt: z.string().datetime(),
});
// Infer TypeScript type from schema
type User = z.infer<typeof userSchema>;
// Partial and Pick utilities
const partialUser = userSchema.partial(); // All fields optional
const requiredUser = userSchema.required(); // All fields required
const pickedUser = userSchema.pick({ email: true, name: true });
const omittedUser = userSchema.omit({ createdAt: true });
```
### Array Schemas
```typescript
// Basic array
const stringArray = z.array(z.string());
// With constraints
const nonEmptyArray = z.array(z.string()).nonempty();
const limitedArray = z.array(z.number()).min(1).max(10);
// Tuple (fixed length, different types)
const coordinate = z.tuple([z.number(), z.number()]);
```
## API Response Validation
### Pattern: Validate API Responses
```typescript
// Define response schema
const apiResponseSchema = z.object({
data: z.object({
items: z.array(userSchema),
total: z.number(),
page: z.number(),
pageSize: z.number(),
}),
meta: z.object({
timestamp: z.string().datetime(),
requestId: z.string().uuid(),
}),
});
// In Angular service
@Injectable({ providedIn: 'root' })
export class UserService {
#http = inject(HttpClient);
#logger = logger({ component: 'UserService' });
getUsers(): Observable<User[]> {
return this.#http.get('/api/users').pipe(
map((response) => {
const result = apiResponseSchema.safeParse(response);
if (!result.success) {
this.#logger.error('Invalid API response', {
errors: result.error.errors
});
throw new Error('Invalid API response');
}
return result.data.data.items;
})
);
}
}
```
### Pattern: Coerce Types
```typescript
// API returns string IDs, coerce to number
const productSchema = z.object({
id: z.coerce.number(), // "123" -> 123
price: z.coerce.number(), // "99.99" -> 99.99
inStock: z.coerce.boolean(), // "true" -> true
createdAt: z.coerce.date(), // "2024-01-01" -> Date
});
```
## Form Validation
### Pattern: Form Schema
```typescript
// Define form schema with custom error messages
const loginFormSchema = z.object({
email: z.string()
.email({ message: 'Invalid email address' }),
password: z.string()
.min(8, { message: 'Password must be at least 8 characters' })
.regex(/[A-Z]/, { message: 'Must contain uppercase letter' })
.regex(/[0-9]/, { message: 'Must contain number' }),
rememberMe: z.boolean().default(false),
});
// Use with Angular forms
type LoginForm = z.infer<typeof loginFormSchema>;
```
### Pattern: Cross-field Validation
```typescript
const passwordFormSchema = z.object({
password: z.string().min(8),
confirmPassword: z.string(),
}).refine(
(data) => data.password === data.confirmPassword,
{
message: "Passwords don't match",
path: ['confirmPassword'], // Error path
}
);
```
## Type Guards
### Pattern: Create Type Guard from Schema
```typescript
// Schema
const customerSchema = z.object({
type: z.literal('customer'),
customerId: z.string(),
loyaltyPoints: z.number(),
});
// Type guard function
function isCustomer(value: unknown): value is z.infer<typeof customerSchema> {
return customerSchema.safeParse(value).success;
}
// Usage
if (isCustomer(data)) {
console.log(data.loyaltyPoints); // Type-safe access
}
```
### Pattern: Discriminated Unions
```typescript
const customerSchema = z.object({
type: z.literal('customer'),
customerId: z.string(),
});
const guestSchema = z.object({
type: z.literal('guest'),
sessionId: z.string(),
});
const userSchema = z.discriminatedUnion('type', [
customerSchema,
guestSchema,
]);
type User = z.infer<typeof userSchema>;
// User = { type: 'customer'; customerId: string } | { type: 'guest'; sessionId: string }
```
## Replacing `any` Types
### Before (unsafe)
```typescript
function processOrder(order: any) {
// No type safety
console.log(order.items.length);
console.log(order.customer.name);
}
```
### After (with Zod)
```typescript
const orderSchema = z.object({
id: z.string().uuid(),
items: z.array(z.object({
productId: z.string(),
quantity: z.number().positive(),
price: z.number().nonnegative(),
})),
customer: z.object({
name: z.string(),
email: z.string().email(),
}),
status: z.enum(['pending', 'confirmed', 'shipped', 'delivered']),
});
type Order = z.infer<typeof orderSchema>;
function processOrder(input: unknown): Order {
const order = orderSchema.parse(input); // Throws if invalid
console.log(order.items.length); // Type-safe
console.log(order.customer.name); // Type-safe
return order;
}
```
## Error Handling
### Pattern: Structured Error Handling
```typescript
const result = schema.safeParse(data);
if (!result.success) {
// Access formatted errors
const formatted = result.error.format();
// Access flat error list
const flat = result.error.flatten();
// Custom error mapping
const errors = result.error.errors.map(err => ({
field: err.path.join('.'),
message: err.message,
code: err.code,
}));
}
```
## Transform Patterns
### Pattern: Transform on Parse
```typescript
const userInputSchema = z.object({
email: z.string().email().transform(s => s.toLowerCase()),
name: z.string().transform(s => s.trim()),
tags: z.string().transform(s => s.split(',')),
});
// Input: { email: "USER@EXAMPLE.COM", name: " John ", tags: "a,b,c" }
// Output: { email: "user@example.com", name: "John", tags: ["a", "b", "c"] }
```
### Pattern: Default Values
```typescript
const configSchema = z.object({
theme: z.enum(['light', 'dark']).default('light'),
pageSize: z.number().default(20),
features: z.array(z.string()).default([]),
});
```
## Best Practices
1. **Define schemas at module boundaries** - API services, form handlers
2. **Use `safeParse` for error handling** - Don't let validation throw unexpectedly
3. **Infer types from schemas** - Single source of truth
4. **Add meaningful error messages** - Help debugging and user feedback
5. **Use transforms for normalization** - Clean data on parse
6. **Keep schemas close to usage** - Colocate with services/components

9
.gitignore vendored
View File

@@ -75,8 +75,11 @@ storybook-static
vite.config.*.timestamp*
vitest.config.*.timestamp*
.mcp.json
.memory.json
nx.instructions.md
CLAUDE.md
*.pyc
.vite
reports/
# Local iPad dev setup (proxy)
/local-dev/

22
.mcp.json Normal file
View File

@@ -0,0 +1,22 @@
{
"mcpServers": {
"context7": {
"type": "http",
"url": "https://mcp.context7.com/mcp"
},
"nx-mcp": {
"type": "stdio",
"command": "npx",
"args": ["nx", "mcp"]
},
"angular-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@angular/cli", "mcp"]
},
"figma-desktop": {
"type": "http",
"url": "http://127.0.0.1:3845/mcp"
}
}
}

1
.nvmrc Normal file
View File

@@ -0,0 +1 @@
v22.20.0

13
AGENTS.md Normal file
View File

@@ -0,0 +1,13 @@
<!-- nx configuration start-->
<!-- Leave the start & end comments to automatically receive updates. -->
# General Guidelines for working with Nx
- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
- You have access to the Nx MCP server and its tools, use them to help the user
- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
<!-- nx configuration end-->

139
CHANGELOG.md Normal file
View File

@@ -0,0 +1,139 @@
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- (checkout-reward) Disable and hide delivery options for reward feature purchases
- (purchase-options) Add disabledPurchaseOptions with flexible visibility control
- (reward-catalog) Pre-select in-store option for reward purchases
- (checkout) Complete reward order confirmation with reusable product info component
- (checkout) Implement reward order confirmation UI and confirmation list item action card component
- (checkout) Add reward order confirmation feature with schema migrations
- (stock-info) Implement request batching with BatchingResource
- (crm) Introduce PrimaryCustomerCardResource and format-name utility
- Angular template skill for modern template patterns
- Tailwind ISA design system skill
### Changed
- (checkout-reward) Implement hierarchical grouping on rewards order confirmation
- (checkout) Move reward selection helpers to data-access for reusability
- (common) Add validation for notification channel flag combinations
- (customer) Merge continueReward and continue methods into unified flow
- Comprehensive CLAUDE.md overhaul with library reference system
- Add Claude Code agents, commands, and skills infrastructure
### Fixed
- (checkout) Resolve currency constraint violations in price handling
- (checkout) Add complete price structure for reward delivery orders
- (checkout) Correct reward output desktop/mobile layout and add insufficient stock warnings
- (customer-card) Implement navigation flow from customer card to reward search
- (purchase-options) Correct customer features mapping
- (reward-order-confirmation) Group items by item-level delivery type
- (reward-order-confirmation) Correct typo and add loading state to collect button
- (reward-confirmation) Improve action card visibility and status messages
- (reward-selection-pop-up) Fix width issue
## [4.2] - 2025-10-23
### Added
- (checkout-reward) Add reward checkout feature (#5258)
- (crm) Add crm-data-access library with initial component and tests
- (shared-filter) Add canApply input to filter input menu components
- Architecture Decision Records (ADRs) documentation
- Error handling and validation infrastructure enhancements
### Changed
- (tabs) Implement backwards compatibility for Process → Tabs migration
- (notifications) Update remission path logic to use Date.now()
- (customer-card) Deactivate Create Customer with Card feature
- Update package.json and recreate package-lock.json for npm@11.6
- Disable markdown format on save in VSCode settings
### Fixed
- (process) Simulate "old tab logic" for compatibility
- (tabs) Correct singleton tabs interaction with new tab areas
- (remission-list) Prioritize reload trigger over exact search
- (remission-list-item, remission-list-empty-state) Improve empty state handling
## [4.1] - 2025-10-06
### Added
- (isa-app) Migrate remission navigation to tab-based routing system
- (utils) Add scroll-top button component
- (remission-list, empty-state) Add comprehensive empty state handling with user guidance
- (remission) Ensure package assignment before completing return receipts
- (libs-ui-dialog-feedback-dialog) Add auto-close functionality with configurable delay
- (old-ui-tooltip) Add pointer-events-auto to tooltip panel
### Changed
- (remission-list) Improve item update handling and UI feedback
- (remission-list, search-item-to-remit-dialog) Simplify dialog flow by removing intermediate steps
### Fixed
- (remission-list) Ensure list reload after search dialog closes
- (remission-list) Auto-select single search result when remission started
- (remission-list, remission-return-receipt-details, libs-dialog) Improve error handling with dedicated error dialog
- (remission-error) Simplify error handling in remission components
- (remission) Filter search results by stock availability and display stock info
- (remission-list, remission-data-access) Add impediment comment and remaining quantity tracking
- (remission-quantity-and-reason-item) Correct quantity input binding and dropdown behavior
- (remission-quantity-reason) Correct dropdown placeholder and remove hardcoded values
- (remission-filter-label) Improve filter button label display and default text
- (remission-data-access) Remove automatic date defaulting in fetchRemissions
- (remission-shared-search-item-to-remit-dialog) Display context-aware feedback on errors
- (isa-app-shell) Improve navigation link targeting for remission sub-routes
- (oms-data-access) Adjust tolino return eligibility logic for display damage
- (ui-input-controls-dropdown) Prevent multiple dropdowns from being open simultaneously
## [4.0] - 2025-07-23
### Added
- (oms-data-access) Initial implementation of OMS data access layer
- (oms-return-review) Implement return review feature
- (print-button) Implement reusable print button component with service integration
- (scanner) Add full-screen scanner styles and components
- (product-router-link) Add shared product router link directive and builder
- (tooltip) Add tooltip component and directive with customizable triggers
- (shared-scanner) Move scanner to shared/scanner location
- (common-data-access) Add takeUntil operators for keydown events
### Changed
- (oms-return-review, oms-return-summary) Fix return receipt mapping and ensure process completion
- (ui-tooltip) Remove native title attribute from tooltip icon host
- (oms-return-details) Improve layout and styling of order group item controls
- (searchbox) Improve formatting and add showScannerButton getter
- (libs-ui-item-rows) Improve data value wrapping and label sizing
- (shared-filter, search-bar, search-main) Add E2E data attributes for filtering and search
### Fixed
- (return-details) Update email validation and improve error handling
- (return-details) Correct storage key retrieval in ReturnDetailsStore
- (return-details) Small layout fix (#5171)
- (isa-app-moment-locale) Correct locale initialization for date formatting
- (oms-return-search) Fix display and logic issues in return search results
- (oms-return-search) Resolve issues in return search result item rendering
- (oms-task-list-item) Address styling and layout issues in return task list
- (ui-dropdown) Improve dropdown usability and conditional rendering
- (return-search) Correct typo in tooltip content
- (libs-shared-filter) Improve date range equality for default filter inputs
## [3.4] - 2025-02-10
_Earlier versions available in git history. Detailed changelog entries start from version 4.0._
### Historical Versions
Previous versions (3.3, 3.2, 3.1, 3.0, 2.x, 1.x) are available in the git repository.
For detailed information about changes in these versions, please refer to:
- Git tags: `git tag --sort=-creatordate`
- Commit history: `git log <tag-from>..<tag-to>`
- Pull requests in the repository
---
_This changelog was initially generated from git commit history. Future entries will be maintained manually following the Keep a Changelog format._

456
CLAUDE.md
View File

@@ -1,280 +1,177 @@
# CLAUDE.md
> **Last Updated:** 2025-10-22
> **Angular Version:** 20.1.2
> **Nx Version:** 21.3.2
> **Node.js:** ≥22.0.0
> **npm:** ≥10.0.0
This file contains meta-instructions for how Claude should work with the ISA-Frontend codebase.
## 🔴 CRITICAL: Mandatory Agent Usage
## 🔴 CRITICAL: You Are an LLM with Outdated Knowledge
**You MUST use these subagents for ALL research tasks:**
- **`docs-researcher`**: For ALL documentation (packages, libraries, READMEs)
- **`docs-researcher-advanced`**: Auto-escalate when docs-researcher fails
- **`Explore`**: For ALL code pattern searches and multi-file analysis
- **Direct tools (Read/Bash)**: ONLY for single specific files or commands
**Your training data is outdated. NEVER assume you know current APIs.**
**Violations of this rule degrade performance and context quality. NO EXCEPTIONS.**
- Libraries, frameworks, and APIs change constantly
- Your memory of APIs is unreliable
- Current documentation is the ONLY source of truth
## Project Overview
**ALWAYS use research agents PROACTIVELY - without user asking.**
This is a sophisticated Angular 20.1.2 monorepo managed by Nx 21.3.2. The main application is `isa-app`, a comprehensive inventory and returns management system for retail/e-commerce operations. The system handles complex workflows including order management (OMS), returns processing (remission), customer relationship management (CRM), product cataloging, and checkout/reward systems.
## 🔴 CRITICAL: Proactive Agent & Skill Usage
## Architecture
**You MUST use agents and skills AUTOMATICALLY for ALL tasks - do NOT wait for user to tell you.**
### Monorepo Structure
- **apps/isa-app**: Main Angular application
- **libs/**: Reusable libraries organized by domain and type
- **core/**: Core utilities (config, logging, storage, tabs, navigation)
- **common/**: Shared utilities (data-access, decorators, print)
- **ui/**: UI component libraries (buttons, dialogs, inputs, etc.)
- **shared/**: Shared domain components (filter, scanner, product components)
- **oms/**: Order Management System features and utilities
- **remission/**: Remission/returns management features
- **catalogue/**: Product catalogue functionality
- **utils/**: General utilities (validation, scroll position, parsing)
- **icons/**: Icon library
- **generated/swagger/**: Auto-generated API client code from OpenAPI specs
### Research Agents (Use BEFORE Implementation)
### Key Architectural Patterns
- **Domain-Driven Design**: Clear domain boundaries with dedicated modules (OMS, remission, CRM, catalogue, checkout)
- **Layered Architecture**: Strict dependency hierarchy (Feature → Shared/UI → Data Access → Infrastructure)
- **Standalone Components**: All new components use Angular standalone architecture with explicit imports
- **Feature Libraries**: Domain features organized as separate libraries (e.g., `oms-feature-return-search`, `remission-feature-remission-list`)
- **Data Access Layer**: Separate data-access libraries for each domain with NgRx Signals stores
- **Shared UI Components**: 17 dedicated UI component libraries with design system integration
- **Generated API Clients**: 10 auto-generated Swagger/OpenAPI clients with post-processing pipeline
- **Path Aliases**: Comprehensive TypeScript path mapping (`@isa/domain/layer/feature`)
- **Component Prefixes**: Domain-specific prefixes (OMS: `oms-feature-*`, Remission: `remi-*`, UI: `ui-*`)
- **Modern State Management**: NgRx Signals with entities, session persistence, and reactive patterns
| Agent | Auto-Invoke When | User Interaction |
|-------|------------------|------------------|
| `docs-researcher` | ANY external library/API usage | NONE - just do it |
| `docs-researcher-advanced` | Implementation fails OR docs-researcher insufficient | NONE - just do it |
| `Explore` | Need codebase patterns or multi-file analysis | NONE - just do it |
## Common Development Commands
### Essential Commands (Project-Specific)
```bash
# Start development server with SSL (required for authentication flows)
npm start
# Run tests for all libraries (excludes main app)
npm test
# Build for development
npm run build
# Build for production
npm run build-prod
# Regenerate all API clients from Swagger/OpenAPI specs
npm run generate:swagger
# Regenerate library reference documentation
npm run docs:generate
# Format code with Prettier
npm run prettier
# Format only staged files (pre-commit hook)
npm run pretty-quick
# Run CI tests with coverage
npm run ci
**Research-First Flow (Mandatory):**
```
Task involves external API? → AUTO-INVOKE docs-researcher
Implement based on docs
Failed? → AUTO-INVOKE docs-researcher-advanced
Still failed? → ASK USER for guidance
```
### Standard Nx Commands
For complete command reference, see [Nx Documentation](https://nx.dev/reference/commands).
### Skills (Use DURING Implementation)
**Common patterns:**
```bash
# Test specific library (always use --skip-nx-cache)
npx nx test <project-name> --skip-nx-cache
| Trigger | Auto-Invoke Skill |
|---------|-------------------|
| Writing Angular templates | `angular-template` |
| Writing HTML with interactivity | `html-template` |
| Applying Tailwind classes | `tailwind` |
| Writing any Angular code | `logging` |
| Creating CSS animations | `css-keyframes-animations` |
| Creating new library | `library-scaffolder` |
| Regenerating API clients | `swagger-sync-manager` |
| Git operations | `git-workflow` |
# Lint a project
npx nx lint <project-name>
# Show project dependencies
npx nx graph
# Run tests for affected projects (CI/CD)
npx nx affected:test --skip-nx-cache
**Skill chaining for Angular work:**
```
angular-template → html-template → logging → tailwind
```
**Important:** Always use `--skip-nx-cache` flag when running tests to ensure fresh results.
### Implementation Agents (Use for Complex Tasks)
## Testing Framework
| Agent | Auto-Invoke When |
|-------|------------------|
| `angular-developer` | Creating components, services, stores (2-5 files) |
| `test-writer` | Writing tests, adding coverage |
| `refactor-engineer` | Refactoring 5+ files, migrations |
> **Last Reviewed:** 2025-10-22
> **Status:** Migration in Progress (Jest → Vitest)
### Anti-Patterns (FORBIDDEN)
### Current Setup (Migration in Progress)
- **Jest**: 40 libraries (65.6% - legacy/existing code)
- **Vitest**: 21 libraries (34.4% - new standard)
- All formal libraries now have test executors configured
### Testing Strategy
- **New libraries**: Use Vitest + Angular Testing Utilities (TestBed, ComponentFixture)
- **Legacy libraries**: Continue with Jest + Spectator until migrated
- **Advanced mocking**: Use ng-mocks for complex scenarios
### Key Requirements
- Test files must end with `.spec.ts`
- Use AAA pattern (Arrange-Act-Assert)
- **Always include E2E attributes**: `data-what`, `data-which`, and dynamic `data-*` in HTML templates
- Mock external dependencies appropriately for your framework
**For detailed testing guidelines, framework comparison, and migration instructions, see [`docs/guidelines/testing.md`](docs/guidelines/testing.md).**
**References:**
- [Jest Documentation](https://jestjs.io/)
- [Vitest Documentation](https://vitest.dev/)
- [Angular Testing Guide](https://angular.io/guide/testing)
- [Spectator](https://ngneat.github.io/spectator/)
## State Management
- **NgRx Signals**: Primary state management with modern functional approach using `signalStore()`
- **Entity Management**: Uses `withEntities()` for normalized data storage
- **Session Persistence**: State persistence with `withStorage()` using SessionStorageProvider
- **Reactive Methods**: `rxMethod()` with `takeUntilKeydownEscape()` for user-cancellable operations
- **Custom RxJS Operators**: Specialized operators like `takeUntilAborted()`, `takeUntilKeydown()`
- **Error Handling**: `tapResponse()` for handling success/error states in stores
- **Lifecycle Hooks**: `withHooks()` for cleanup and initialization (e.g., orphaned entity cleanup)
- **Navigation State**: Use `@isa/core/navigation` for temporary navigation context (return URLs, wizard state) instead of query parameters
## Styling and Design System
- **Framework**: [Tailwind CSS](https://tailwindcss.com/docs) with extensive ISA-specific customization
- **Custom Breakpoints**: `isa-desktop` (1024px), `isa-desktop-l` (1440px), `isa-desktop-xl` (1920px)
- **Brand Color System**: `isa-*` color palette with semantic naming
- **Custom Tailwind Plugins** (7): button, typography, menu, label, input, section, select-bullet
- **Typography System**: 14 custom utilities (`.isa-text-heading-1-bold`, `.isa-text-body-2-regular`, etc.)
- **UI Component Libraries**: 17 specialized libraries with consistent APIs (see Library Reference)
- **Storybook**: Component documentation and development at `npm run storybook`
### Responsive Design with Breakpoint Service
Use `@isa/ui/layout` for reactive breakpoint detection instead of CSS-only solutions:
```typescript
import { breakpoint, Breakpoint } from '@isa/ui/layout';
// Detect screen size reactively
isDesktop = breakpoint([Breakpoint.Desktop, Breakpoint.DekstopL, Breakpoint.DekstopXL]);
```
❌ Implementing without researching first
❌ Asking "should I research this?" - just do it
❌ Asking "should I use a skill?" - just do it
❌ Trial and error: implement → fail → try again → fail
❌ Writing Angular code without loading skills first
```
**Available Breakpoints:**
- `Tablet`: max-width: 1279px (mobile/tablet)
- `Desktop`: 1280px - 1439px (standard desktop)
- `DekstopL`: 1440px - 1919px (large desktop)
- `DekstopXL`: 1920px+ (extra large)
### Correct Pattern
**Template Usage:**
```html
@if (isDesktop) {
<!-- Desktop-specific content -->
}
```
✅ "Researching [library] API..." → [auto-invokes docs-researcher]
✅ "Loading angular-template skill..." → [auto-invokes skill]
✅ "Implementing based on current docs..."
✅ If fails: "Escalating research..." → [auto-invokes docs-researcher-advanced]
```
**Why:** Prefer breakpoint service over CSS-only (hidden/flex) for SSR and maintainability.
## Communication Guidelines
## API Integration and Data Access
- Keep answers concise and focused
- Use bullet points and structured formatting
- Skip verbose explanations unless requested
- Focus on what the user needs, not everything you know
**Generated Swagger Clients:** 10 auto-generated TypeScript clients in `generated/swagger/`
- Available APIs: availability-api, cat-search-api, checkout-api, crm-api, eis-api, inventory-api, isa-api, oms-api, print-api, wws-api
- Tool: [ng-swagger-gen](https://www.npmjs.com/package/ng-swagger-gen) with custom per-API configuration
- Post-processing: Automatic Unicode cleanup via `tools/fix-files.js`
- Regenerate: `npm run generate:swagger`
## Context Management
**Architecture Pattern:**
- Business logic services wrap generated API clients
- Type safety: TypeScript + [Zod](https://zod.dev/) schema validation
- Error handling: Global HTTP interceptor with automatic re-authentication
- Modern injection: Uses `inject()` function with private field pattern
- Request cancellation: Built-in via AbortSignal and custom RxJS operators (`takeUntilAborted()`, `takeUntilKeydown()`)
**Context bloat kills reliability. Minimize aggressively.**
**Data Access Libraries:** See Library Reference section for domain-specific implementations (`@isa/[domain]/data-access`).
### Tool Result Minimization
## Build Configuration
- **Framework**: Angular with TypeScript (see `package.json` for current versions)
- **Requirements**:
- Node.js >= 22.0.0 (specified in package.json engines)
- npm >= 10.0.0 (specified in package.json engines)
- **Build System**: Nx monorepo with Vite for testing (Vitest)
- **Development Server**: Serves with SSL by default (required for authentication flows)
| Tool | Keep | Discard |
|------|------|---------|
| Bash (success) | `✓ Command succeeded` | Full output |
| Bash (failure) | Exit code + error (max 10 lines) | Verbose output |
| Edit | `✓ Modified file.ts` | Full diffs |
| Read | Extracted relevant section | Full file content |
| Agent results | 1-2 sentence summary | Raw JSON/full output |
## Important Conventions and Patterns
### Agent Result Handling
### Library Organization
- **Naming Pattern**: `[domain]-[layer]-[feature]` (e.g., `oms-feature-return-search`, `ui-buttons`)
- **Path Aliases**: `@isa/[domain]/[layer]/[feature]` (e.g., `@isa/oms/data-access`, `@isa/ui/buttons`)
- **Project Names**: Found in each library's `project.json` file, following consistent naming
```
❌ WRONG: "Docs researcher returned: [huge JSON...]"
✅ RIGHT: "docs-researcher found: Use signalStore() with withState()"
```
### Component Architecture
- **Standalone Components**: All new components must be standalone with explicit imports
- **Component Prefixes**: Domain-specific prefixes for clear identification
- OMS features: `oms-feature-*` (e.g., `oms-feature-return-search-main`)
- Remission features: `remi-*`
- UI components: `ui-*`
- Core utilities: `core-*`
- **Signal-based Inputs**: Use Angular signals (`input()`, `computed()`) for reactive properties
- **Host Binding**: Dynamic CSS classes via Angular host properties
### Session Cleanup
### Dependency Rules
- **Unidirectional Dependencies**: Feature → Shared/UI → Data Access → Infrastructure
- **Import Boundaries**: Use path aliases, avoid relative imports across domain boundaries
- **Generated API Imports**: Import from `@generated/swagger/[api-name]` for API clients
Use `/clear` between unrelated tasks to prevent context degradation.
### Code Quality
- **Modern Angular Patterns**: Prefer `inject()` over constructor injection
- **Type Safety**: Use Zod schemas for runtime validation alongside TypeScript
- **Error Handling**: Custom error classes with specific error codes
- **E2E Testing**: Always include `data-what` and `data-which` attributes in templates
### Long-Running Task Pattern
## Development Workflow and Best Practices
For complex tasks approaching context limits:
1. Dump progress to a `.md` file (e.g., `progress.md`)
2. Use `/clear` to reset context
3. Resume by reading the progress file
4. Continue from where you left off
### Project Conventions
- **Default Branch**: `develop` (not main) - Always create PRs against develop
- **Commit Style**: [Conventional commits](https://www.conventionalcommits.org/) without co-author tags
- **Nx Cache**: Always use `--skip-nx-cache` for tests to ensure fresh results
- **Testing**: New libraries use Vitest + Angular Testing Utilities; legacy use Jest + Spectator
- **E2E Attributes**: Always include `data-what`, `data-which`, and dynamic `data-*` in templates
- **Design System**: Use ISA-specific Tailwind utilities (`isa-accent-*`, `isa-text-*`)
### Context Monitoring
### Code Quality Tools
- **Linting**: [ESLint](https://eslint.org/) with Nx dependency checks
- **Formatting**: [Prettier](https://prettier.io/) with Husky + lint-staged pre-commit hooks
- **Type Safety**: [TypeScript](https://www.typescriptlang.org/) strict mode + [Zod](https://zod.dev/) validation
- **Bundle Size**: Monitor carefully (2MB warning, 5MB error for main bundle)
- Use `/context` to check current token usage
- Fresh session baseline: ~20k tokens
- Consider `/compact` when approaching 150k tokens
- Prefer `/clear` over `/compact` when starting new topics
### Nx Workflow Tips
- Use `npx nx graph` to visualize dependencies
- Use `npx nx affected:test` for CI/CD optimization
- Reference: [Nx Documentation](https://nx.dev/getting-started/intro)
## Extended Thinking
## Development Notes and Guidelines
Use progressive thinking depth for complex analysis:
### Getting Started
- **Application Startup**: Only `isa-app` can be started - it's the main application entry point
- **SSL Development**: The development server runs with SSL by default (`npm start`), which is crucial for production-like authentication flows
- **Node Requirements**: Ensure Node.js ≥22.0.0 and npm ≥10.0.0 before starting development
- **First-Time Setup**: After cloning, run `npm install` then `npm start` to verify everything works
| Trigger | Thinking Budget | Use Case |
|---------|----------------|----------|
| `"think"` | ~4k tokens | Basic analysis, simple decisions |
| `"think hard"` | ~10k tokens | Moderate complexity, multi-factor decisions |
| `"think harder"` | ~16k tokens | Deep analysis, architectural decisions |
| `"ultrathink"` | ~32k tokens | Maximum depth, critical planning |
### Essential Documentation References
- **Testing Guidelines**: Review `docs/guidelines/testing.md` before writing any tests - it covers the Jest→Vitest migration, Spectator→Angular Testing Utilities transition, and E2E attribute requirements
- **Code Review Standards**: Follow the structured review process in `.github/review-instructions.md` with categorized feedback (🚨 Critical, ❗ Minor, ⚠️ Warnings, ✅ Good Practices)
- **E2E Testing Requirements**: Always include `data-what`, `data-which`, and dynamic `data-*` attributes in HTML templates - these are essential for automated testing by QA colleagues
**Examples:**
- "Think about how to structure this component"
- "Think hard about the best approach for state management"
- "Ultrathink about the architecture for this feature"
### Researching and Investigating the Codebase
## Code Investigation (MANDATORY)
**🔴 MANDATORY: You MUST use subagents for research. Direct file reading/searching is FORBIDDEN except for single specific files.**
**Never speculate about code you haven't read.**
#### Required Agent Usage
If user references a specific file:
1. **READ the file first** using the Read tool
2. **THEN provide analysis** based on actual contents
3. If file doesn't exist, **say so explicitly**
| Task Type | Required Agent | Escalation Path |
|-----------|---------------|-----------------|
| **Package/Library Documentation** | `docs-researcher` | → `docs-researcher-advanced` if not found |
| **Internal Library READMEs** | `docs-researcher` | Keep context clean |
| **Code Pattern Search** | `Explore` | Set thoroughness level |
| **Implementation Analysis** | `Explore` | Multiple file analysis |
| **Single Specific File** | Read tool directly | No agent needed |
**Anti-Hallucination Rules:**
- Never describe code you haven't opened
- Never assume file contents based on names
- Never guess API signatures without documentation
- Always verify imports and dependencies exist
#### Documentation Research System (Two-Tier)
## Implementation Decisions
| Task Type | Required Agent | Escalation Path |
| --------------------------------- | ------------------ | ----------------------------------------- |
| **Package/Library Documentation** | `docs-researcher` | → `docs-researcher-advanced` if not found |
| **Internal Library READMEs** | `docs-researcher` | Keep context clean |
| **Monorepo Library Overview** | `docs-researcher` | Uses `docs/library-reference.md` |
| **Code Pattern Search** | `Explore` | Set thoroughness level |
| **Implementation Analysis** | `Explore` | Multiple file analysis |
| **Single Specific File** | Read tool directly | No agent needed |
**Note:** The `docs-researcher` agent uses `docs/library-reference.md` as a primary index for discovering monorepo libraries. This file contains descriptions and locations for all libraries, enabling quick library discovery without reading individual READMEs.
### Documentation Research System (Two-Tier)
1. **ALWAYS start with `docs-researcher`** (Haiku, 30-120s) for any documentation need
2. **Auto-escalate to `docs-researcher-advanced`** (Sonnet, 2-7min) when:
@@ -283,75 +180,60 @@ isDesktop = breakpoint([Breakpoint.Desktop, Breakpoint.DekstopL, Breakpoint.Deks
- Need code inference
- Complex architectural questions
#### Enforcement Examples
### When to Use Agents vs Direct Tools
```
❌ WRONG: Read libs/ui/buttons/README.md
✅ RIGHT: Task → docs-researcher"Find documentation for @isa/ui/buttons"
❌ WRONG: Grep for "signalStore" patterns
✅ RIGHT: Task → Explore → "Find all signalStore implementations"
❌ WRONG: WebSearch for Zod documentation
✅ RIGHT: Task → docs-researcher → "Find Zod validation documentation"
Single known file? → Read tool directly
Code pattern search?Explore agent
Documentation lookup? → docs-researcher agent
Creating 2-5 Angular files? → angular-developer agent
Refactoring 5+ files? → refactor-engineer agent
Simple 1-file edit? → Direct implementation
```
**Remember: Using subagents is NOT optional - it's mandatory for maintaining context efficiency and search quality.**
### Proactive Agent Triggers
#### Common Research Patterns
**Auto-invoke `angular-developer` when user says:**
- "Create component/service/store/pipe/directive/guard"
- Task touches 2-5 Angular files
| Information Need | Required Approach |
|-----------------|-------------------|
| **Library documentation** | `docs-researcher` → Check library-reference.md → Escalate if needed |
| **Code patterns/examples** | `Explore` with "medium" or "very thorough" |
| **Architecture understanding** | `npx nx graph` + `Explore` for implementation |
| **Debugging/errors** | Direct tool use (Read specific error file, check console) |
**Auto-invoke `test-writer` when user says:**
- "Write tests", "Add coverage"
#### Debugging Tips
- **TypeScript errors**: Follow error path to exact file:line
- **Test failures**: Use `--skip-nx-cache` for fresh output
- **Module resolution**: Check `tsconfig.base.json` path aliases
- **State issues**: Use Angular DevTools browser extension
**Auto-invoke `refactor-engineer` when user says:**
- "Refactor all", "Migrate X files", "Update pattern across"
### Library Development Patterns
- **Library Documentation**: Use `docs-researcher` for ALL library READMEs (mandatory for context management)
- **New Library Creation**: Use Nx generators with domain-specific naming (`[domain]-[layer]-[feature]`)
- **Standalone Components**: All new components must be standalone with explicit imports - no NgModules
- **Testing Framework**: New = Vitest + Angular Testing Utilities, Legacy = Jest + Spectator
- **Path Aliases**: Always use `@isa/[domain]/[layer]/[feature]` - avoid relative imports
**Auto-invoke `context-manager` when user says:**
- "Remember to", "TODO:", "Don't forget"
#### Library Reference Guide
## Agent Communication
The monorepo contains **62 libraries** organized across 12 domains. For quick lookup, see **[`docs/library-reference.md`](docs/library-reference.md)**.
### Briefing Agents
**Quick Overview by Domain:**
- Availability (1) | Catalogue (1) | Checkout (6) | Common (3) | Core (5) | CRM (1) | Icons (1)
- OMS (9) | Remission (8) | Shared Components (7) | UI Components (17) | Utilities (3)
Keep briefings focused:
```
Implement: [type] at [path]
Purpose: [1 sentence]
Requirements: [list]
```
### API Integration Workflow
- **Swagger Generation**: Run `npm run generate:swagger` to regenerate all 10 API clients when backend changes
- **Data Services**: Wrap generated API clients in domain-specific data-access services with proper error handling and Zod validation
- **State Management**: Use NgRx Signals with `signalStore()`, entity management, and session persistence for complex state
### Agent Results
### Performance and Quality Considerations
- **Bundle Monitoring**: Watch bundle sizes (2MB warning, 5MB error for main bundle)
- **Testing Cache**: Always use `--skip-nx-cache` flag when running tests to ensure reliable results
- **Code Quality**: Pre-commit hooks enforce Prettier formatting and ESLint rules automatically
- **Memory Management**: Clean up subscriptions and use OnPush change detection for optimal performance
Extract only what's needed, discard the rest:
```
✓ Created 3 files
✓ Tests: 12/12 passing
✓ Skills applied: angular-template, logging
```
### Common Troubleshooting
- **Build Issues**: Check Node version and run `npm install` if encountering module resolution errors
- **Test Failures**: Use `--skip-nx-cache` flag and ensure test isolation (no shared state between tests)
- **Nx Cache Issues**: If you see `existing outputs match the cache, left as is` during build or testing:
- **Option 1**: Run `npx nx reset` to clear the Nx cache completely
- **Option 2**: Use `--skip-nx-cache` flag to bypass Nx cache for a specific command (e.g., `npx nx test <project> --skip-nx-cache`)
- **When to use**: Always use `--skip-nx-cache` when you need guaranteed fresh builds or test results
- **SSL Certificates**: Development server uses SSL - accept certificate warnings in browser for localhost
- **Import Errors**: Verify path aliases in `tsconfig.base.json` and use absolute imports for cross-library dependencies
<!-- nx configuration start-->
<!-- Leave the start & end comments to automatically receive updates. -->
### Domain-Specific Conventions
- **Component Prefixes**: Use `oms-feature-*` for OMS, `remi-*` for remission, `ui-*` for shared components
- **Git Workflow**: Default branch is `develop` (not main), use conventional commits without co-author tags
- **Design System**: Use ISA-specific Tailwind utilities (`isa-accent-*`, `isa-text-*`) and custom breakpoints (`isa-desktop-*`)
- **Logging**: Use centralized logging service (`@isa/core/logging`) with contextual information for debugging
- **Navigation State**: Use `@isa/core/navigation` for passing temporary state between routes (return URLs, form context) instead of query parameters - keeps URLs clean and state reliable
# General Guidelines for working with Nx
- Run tasks through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of underlying tooling
- Use `nx_workspace` tool to understand workspace architecture
- Use `nx_project_details` for specific project structure
- Use `nx_docs` for nx configuration questions
<!-- nx configuration end-->

View File

@@ -1,4 +1,8 @@
import type { Preview } from '@storybook/angular';
import { registerLocaleData } from '@angular/common';
import localeDe from '@angular/common/locales/de';
registerLocaleData(localeDe);
const preview: Preview = {
tags: ['autodocs'],

View File

@@ -1,162 +1,162 @@
{
"name": "isa-app",
"$schema": "../../node_modules/nx/schemas/project-schema.json",
"projectType": "application",
"prefix": "app",
"sourceRoot": "apps/isa-app/src",
"tags": [],
"targets": {
"build": {
"executor": "@angular-devkit/build-angular:application",
"options": {
"allowedCommonJsDependencies": [
"lodash",
"moment",
"jsrsasign",
"pdfjs-dist/build/pdf",
"pdfjs-dist/web/pdf_viewer",
"pdfjs-dist/es5/build/pdf",
"pdfjs-dist/es5/web/pdf_viewer"
],
"outputPath": "dist/isa-app",
"index": "apps/isa-app/src/index.html",
"browser": "apps/isa-app/src/main.ts",
"polyfills": ["zone.js"],
"tsConfig": "apps/isa-app/tsconfig.app.json",
"inlineStyleLanguage": "scss",
"assets": [
"apps/isa-app/src/favicon.ico",
"apps/isa-app/src/assets",
"apps/isa-app/src/config",
"apps/isa-app/src/silent-refresh.html",
"apps/isa-app/src/manifest.webmanifest",
{
"glob": "**/*",
"input": "node_modules/scandit-web-datacapture-barcode/build/engine",
"output": "scandit"
}
],
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
],
"scripts": []
},
"configurations": {
"production": {
"budgets": [
{
"type": "initial",
"maximumWarning": "2mb",
"maximumError": "5mb"
},
{
"type": "anyComponentStyle",
"maximumWarning": "25kb"
}
],
"fileReplacements": [
{
"replace": "apps/isa-app/src/environments/environment.ts",
"with": "apps/isa-app/src/environments/environment.prod.ts"
}
],
"outputHashing": "all",
"serviceWorker": "apps/isa-app/ngsw-config.json"
},
"development": {
"optimization": false,
"extractLicenses": false,
"sourceMap": true
}
},
"defaultConfiguration": "production",
"outputs": ["{options.outputPath}"]
},
"serve": {
"executor": "@angular-devkit/build-angular:dev-server",
"configurations": {
"production": {
"buildTarget": "isa-app:build:production"
},
"development": {
"buildTarget": "isa-app:build:development"
}
},
"defaultConfiguration": "development",
"continuous": true
},
"extract-i18n": {
"executor": "@angular-devkit/build-angular:extract-i18n",
"options": {
"buildTarget": "isa-app:build"
}
},
"lint": {
"executor": "@nx/eslint:lint"
},
"test": {
"executor": "@nx/jest:jest",
"outputs": ["{workspaceRoot}/coverage/{projectRoot}"],
"options": {
"jestConfig": "apps/isa-app/jest.config.ts"
}
},
"serve-static": {
"executor": "@nx/web:file-server",
"options": {
"buildTarget": "isa-app:build",
"staticFilePath": "dist/apps/isa-app/browser",
"spa": true
}
},
"storybook": {
"executor": "@storybook/angular:start-storybook",
"options": {
"port": 4400,
"configDir": "apps/isa-app/.storybook",
"browserTarget": "isa-app:build",
"compodoc": false,
"open": false,
"assets": [
{
"glob": "**/*",
"input": "apps/isa-app/src/assets",
"output": "/assets"
}
],
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
]
},
"configurations": {
"ci": {
"quiet": true
}
}
},
"build-storybook": {
"executor": "@storybook/angular:build-storybook",
"outputs": ["{options.outputDir}"],
"options": {
"outputDir": "dist/storybook/isa-app",
"configDir": "apps/isa-app/.storybook",
"browserTarget": "isa-app:build",
"compodoc": false,
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
]
},
"configurations": {
"ci": {
"quiet": true
}
}
}
}
}
{
"name": "isa-app",
"$schema": "../../node_modules/nx/schemas/project-schema.json",
"projectType": "application",
"prefix": "app",
"sourceRoot": "apps/isa-app/src",
"tags": ["skip:ci"],
"targets": {
"build": {
"executor": "@angular-devkit/build-angular:application",
"options": {
"allowedCommonJsDependencies": [
"lodash",
"moment",
"jsrsasign",
"pdfjs-dist/build/pdf",
"pdfjs-dist/web/pdf_viewer",
"pdfjs-dist/es5/build/pdf",
"pdfjs-dist/es5/web/pdf_viewer"
],
"outputPath": "dist/isa-app",
"index": "apps/isa-app/src/index.html",
"browser": "apps/isa-app/src/main.ts",
"polyfills": ["zone.js"],
"tsConfig": "apps/isa-app/tsconfig.app.json",
"inlineStyleLanguage": "scss",
"assets": [
"apps/isa-app/src/favicon.ico",
"apps/isa-app/src/assets",
"apps/isa-app/src/config",
"apps/isa-app/src/silent-refresh.html",
"apps/isa-app/src/manifest.webmanifest",
{
"glob": "**/*",
"input": "node_modules/scandit-web-datacapture-barcode/build/engine",
"output": "scandit"
}
],
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
],
"scripts": []
},
"configurations": {
"production": {
"budgets": [
{
"type": "initial",
"maximumWarning": "2mb",
"maximumError": "5mb"
},
{
"type": "anyComponentStyle",
"maximumWarning": "25kb"
}
],
"fileReplacements": [
{
"replace": "apps/isa-app/src/environments/environment.ts",
"with": "apps/isa-app/src/environments/environment.prod.ts"
}
],
"outputHashing": "all",
"serviceWorker": "apps/isa-app/ngsw-config.json"
},
"development": {
"optimization": false,
"extractLicenses": false,
"sourceMap": true
}
},
"defaultConfiguration": "production",
"outputs": ["{options.outputPath}"]
},
"serve": {
"executor": "@angular-devkit/build-angular:dev-server",
"configurations": {
"production": {
"buildTarget": "isa-app:build:production"
},
"development": {
"buildTarget": "isa-app:build:development"
}
},
"defaultConfiguration": "development",
"continuous": true
},
"extract-i18n": {
"executor": "@angular-devkit/build-angular:extract-i18n",
"options": {
"buildTarget": "isa-app:build"
}
},
"lint": {
"executor": "@nx/eslint:lint"
},
"test": {
"executor": "@nx/jest:jest",
"outputs": ["{workspaceRoot}/coverage/{projectRoot}"],
"options": {
"jestConfig": "apps/isa-app/jest.config.ts"
}
},
"serve-static": {
"executor": "@nx/web:file-server",
"options": {
"buildTarget": "isa-app:build",
"staticFilePath": "dist/apps/isa-app/browser",
"spa": true
}
},
"storybook": {
"executor": "@storybook/angular:start-storybook",
"options": {
"port": 4400,
"configDir": "apps/isa-app/.storybook",
"browserTarget": "isa-app:build",
"compodoc": false,
"open": false,
"assets": [
{
"glob": "**/*",
"input": "apps/isa-app/src/assets",
"output": "/assets"
}
],
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
]
},
"configurations": {
"ci": {
"quiet": true
}
}
},
"build-storybook": {
"executor": "@storybook/angular:build-storybook",
"outputs": ["{options.outputDir}"],
"options": {
"outputDir": "dist/storybook/isa-app",
"configDir": "apps/isa-app/.storybook",
"browserTarget": "isa-app:build",
"compodoc": false,
"styles": [
"@angular/cdk/overlay-prebuilt.css",
"apps/isa-app/src/tailwind.scss",
"apps/isa-app/src/styles.scss"
]
},
"configurations": {
"ci": {
"quiet": true
}
}
}
}
}

View File

@@ -1,6 +1,5 @@
import { inject, isDevMode, NgModule } from '@angular/core';
import { Location } from '@angular/common';
import { RouterModule, Routes, Router } from '@angular/router';
import { NgModule } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';
import {
CanActivateCartGuard,
CanActivateCartWithProcessIdGuard,
@@ -8,24 +7,17 @@ import {
CanActivateCustomerOrdersGuard,
CanActivateCustomerOrdersWithProcessIdGuard,
CanActivateCustomerWithProcessIdGuard,
CanActivateGoodsInGuard,
CanActivateProductGuard,
CanActivateProductWithProcessIdGuard,
CanActivateRemissionGuard,
CanActivateTaskCalendarGuard,
IsAuthenticatedGuard,
} from './guards';
import { CanActivateAssortmentGuard } from './guards/can-activate-assortment.guard';
import { CanActivatePackageInspectionGuard } from './guards/can-activate-package-inspection.guard';
import { MainComponent } from './main.component';
import { PreviewComponent } from './preview';
import {
BranchSectionResolver,
CustomerSectionResolver,
ProcessIdResolver,
} from './resolvers';
import { TokenLoginComponent, TokenLoginModule } from './token-login';
import { ProcessIdGuard } from './guards/process-id.guard';
import {
ActivateProcessIdGuard,
ActivateProcessIdWithConfigKeyGuard,
@@ -33,9 +25,8 @@ import {
import { MatomoRouteData } from 'ngx-matomo-client';
import {
tabResolverFn,
TabService,
TabNavigationService,
processResolverFn,
hasTabIdGuard,
} from '@isa/core/tabs';
import { provideScrollPositionRestoration } from '@isa/utils/scroll-position';
@@ -77,8 +68,12 @@ const routes: Routes = [
loadChildren: () =>
import('@page/catalog').then((m) => m.PageCatalogModule),
canActivate: [CanActivateProductWithProcessIdGuard],
resolve: { processId: ProcessIdResolver },
resolve: {
processId: ProcessIdResolver,
},
},
// TODO: Check if order and :processId/order is still being used
// If not, remove these routes and the related guards and resolvers
{
path: 'order',
loadChildren: () =>
@@ -90,7 +85,9 @@ const routes: Routes = [
loadChildren: () =>
import('@page/customer-order').then((m) => m.CustomerOrderModule),
canActivate: [CanActivateCustomerOrdersWithProcessIdGuard],
resolve: { processId: ProcessIdResolver },
resolve: {
processId: ProcessIdResolver,
},
},
{
path: 'customer',
@@ -103,7 +100,9 @@ const routes: Routes = [
loadChildren: () =>
import('@page/customer').then((m) => m.CustomerModule),
canActivate: [CanActivateCustomerWithProcessIdGuard],
resolve: { processId: ProcessIdResolver },
resolve: {
processId: ProcessIdResolver,
},
},
{
path: 'cart',
@@ -116,10 +115,13 @@ const routes: Routes = [
loadChildren: () =>
import('@page/checkout').then((m) => m.PageCheckoutModule),
canActivate: [CanActivateCartWithProcessIdGuard],
resolve: {
processId: ProcessIdResolver,
},
},
{
path: 'pickup-shelf',
canActivate: [ProcessIdGuard],
canActivate: [ActivateProcessIdGuard],
// NOTE: This is a workaround for the canActivate guard not being called
loadChildren: () =>
import('@page/pickup-shelf').then((m) => m.PickupShelfOutModule),
@@ -129,6 +131,9 @@ const routes: Routes = [
canActivate: [ActivateProcessIdGuard],
loadChildren: () =>
import('@page/pickup-shelf').then((m) => m.PickupShelfOutModule),
resolve: {
processId: ProcessIdResolver,
},
},
{ path: '**', redirectTo: 'dashboard', pathMatch: 'full' },
],
@@ -144,7 +149,7 @@ const routes: Routes = [
import('@page/task-calendar').then(
(m) => m.PageTaskCalendarModule,
),
canActivate: [CanActivateTaskCalendarGuard],
canActivate: [ActivateProcessIdWithConfigKeyGuard('taskCalendar')],
},
{
path: 'pickup-shelf',
@@ -157,27 +162,23 @@ const routes: Routes = [
path: 'goods/in',
loadChildren: () =>
import('@page/goods-in').then((m) => m.GoodsInModule),
canActivate: [CanActivateGoodsInGuard],
canActivate: [ActivateProcessIdWithConfigKeyGuard('goodsIn')],
},
// {
// path: 'remission',
// loadChildren: () =>
// import('@page/remission').then((m) => m.PageRemissionModule),
// canActivate: [CanActivateRemissionGuard],
// },
{
path: 'package-inspection',
loadChildren: () =>
import('@page/package-inspection').then(
(m) => m.PackageInspectionModule,
),
canActivate: [CanActivatePackageInspectionGuard],
canActivate: [
ActivateProcessIdWithConfigKeyGuard('packageInspection'),
],
},
{
path: 'assortment',
loadChildren: () =>
import('@page/assortment').then((m) => m.AssortmentModule),
canActivate: [CanActivateAssortmentGuard],
canActivate: [ActivateProcessIdWithConfigKeyGuard('assortment')],
},
{ path: '**', redirectTo: 'task-calendar', pathMatch: 'full' },
],
@@ -189,7 +190,7 @@ const routes: Routes = [
path: ':tabId',
component: MainComponent,
resolve: { process: processResolverFn, tab: tabResolverFn },
canActivate: [IsAuthenticatedGuard],
canActivate: [IsAuthenticatedGuard, hasTabIdGuard],
children: [
{
path: 'reward',
@@ -246,13 +247,6 @@ const routes: Routes = [
},
];
if (isDevMode()) {
routes.unshift({
path: 'preview',
component: PreviewComponent,
});
}
@NgModule({
imports: [
RouterModule.forRoot(routes, {

View File

@@ -1,4 +1,5 @@
import { version } from '../../../../package.json';
import { IsaTitleStrategy } from '@isa/common/title-management';
import {
HTTP_INTERCEPTORS,
provideHttpClient,
@@ -56,7 +57,6 @@ import {
ScanditScanAdapterModule,
} from '@adapter/scan';
import * as Commands from './commands';
import { PreviewComponent } from './preview';
import { NativeContainerService } from '@external/native-container';
import { ShellModule } from '@shared/shell';
import { MainComponent } from './main.component';
@@ -68,7 +68,7 @@ import {
matWifiOff,
} from '@ng-icons/material-icons/baseline';
import { NetworkStatusService } from './services/network-status.service';
import { debounceTime, firstValueFrom } from 'rxjs';
import { debounceTime, filter, firstValueFrom, switchMap } from 'rxjs';
import { provideMatomo } from 'ngx-matomo-client';
import { withRouter, withRouteData } from 'ngx-matomo-client';
import {
@@ -77,7 +77,7 @@ import {
LogLevel,
withSink,
ConsoleLogSink,
logger,
logger as loggerFactory,
} from '@isa/core/logging';
import {
IDBStorageProvider,
@@ -85,57 +85,78 @@ import {
UserStorageProvider,
} from '@isa/core/storage';
import { Store } from '@ngrx/store';
import { TabNavigationService } from '@isa/core/tabs';
import { OAuthService } from 'angular-oauth2-oidc';
import z from 'zod';
import { TitleStrategy } from '@angular/router';
import { TabNavigationService } from '@isa/core/tabs';
registerLocaleData(localeDe, localeDeExtra);
registerLocaleData(localeDe, 'de', localeDeExtra);
export function _appInitializerFactory(config: Config, injector: Injector) {
return async () => {
// Get logging service for initialization logging
const logger = loggerFactory(() => ({ service: 'AppInitializer' }));
const statusElement = document.querySelector('#init-status');
const laoderElement = document.querySelector('#init-loader');
try {
logger.info('Starting application initialization');
let online = false;
const networkStatus = injector.get(NetworkStatusService);
while (!online) {
online = await firstValueFrom(networkStatus.online$);
if (!online) {
logger.warn('Waiting for network connection');
statusElement.innerHTML =
'<b>Warte auf Netzwerkverbindung (WLAN)</b><br><br>Bitte prüfen Sie die Netzwerkverbindung (WLAN).<br>Sobald eine Netzwerkverbindung besteht, wird die App automatisch neu geladen.';
await new Promise((resolve) => setTimeout(resolve, 250));
}
}
logger.info('Network connection established');
statusElement.innerHTML = 'Konfigurationen werden geladen...';
logger.info('Loading configurations');
statusElement.innerHTML = 'Scanner wird initialisiert...';
logger.info('Initializing scanner');
const scanAdapter = injector.get(ScanAdapterService);
await scanAdapter.init();
logger.info('Scanner initialized');
statusElement.innerHTML = 'Authentifizierung wird geprüft...';
logger.info('Initializing authentication');
const auth = injector.get(AuthService);
try {
await auth.init();
const authenticated = await auth.init();
if (!authenticated) {
throw new Error('User is not authenticated');
}
} catch {
statusElement.innerHTML = 'Authentifizierung wird durchgeführt...';
logger.info('Performing login');
const strategy = injector.get(LoginStrategy);
await strategy.login();
return;
}
statusElement.innerHTML = 'Native Container wird initialisiert...';
logger.info('Initializing native container');
const nativeContainer = injector.get(NativeContainerService);
await nativeContainer.init();
logger.info('Native container initialized');
statusElement.innerHTML = 'Datenbank wird initialisiert...';
logger.info('Initializing database');
await injector.get(IDBStorageProvider).init();
logger.info('Database initialized');
statusElement.innerHTML = 'Benutzerzustand wird geladen...';
logger.info('Loading user storage');
const userStorage = injector.get(UserStorageProvider);
await userStorage.init();
@@ -144,16 +165,29 @@ export function _appInitializerFactory(config: Config, injector: Injector) {
const state = userStorage.get('store');
if (state && state['version'] === version) {
store.dispatch({ type: 'HYDRATE', payload: userStorage.get('store') });
logger.info('Store hydrated from user storage');
} else {
logger.debug('Store hydration skipped', () => ({
reason: state ? 'version mismatch' : 'no stored state',
}));
}
// Subscribe on Store changes and save to user storage
store.pipe(debounceTime(1000)).subscribe((state) => {
userStorage.set('store', { ...state, version });
});
auth.initialized$
.pipe(
filter((initialized) => initialized),
switchMap(() => store.pipe(debounceTime(1000))),
)
.subscribe((state) => {
userStorage.set('store', state);
});
logger.info('Application initialization completed');
// Inject tab navigation service to initialize it
injector.get(TabNavigationService).init();
} catch (error) {
console.error('Error during app initialization', error);
logger.error('Application initialization failed', error as Error, () => ({
message: (error as Error).message,
}));
laoderElement.remove();
statusElement.classList.add('text-xl');
statusElement.innerHTML +=
@@ -199,7 +233,7 @@ export function _notificationsHubOptionsFactory(
}
const USER_SUB_FACTORY = () => {
const _logger = logger(() => ({
const _logger = loggerFactory(() => ({
context: 'USER_SUB',
}));
const auth = inject(OAuthService);
@@ -237,7 +271,6 @@ const USER_SUB_FACTORY = () => {
CoreCommandModule.forRoot(Object.values(Commands)),
CoreLoggerModule.forRoot(),
AppStoreModule,
PreviewComponent,
AuthModule.forRoot(),
CoreApplicationModule.forRoot(),
UiModalModule.forRoot(),
@@ -297,6 +330,7 @@ const USER_SUB_FACTORY = () => {
useValue: 'EUR',
},
provideUserSubFactory(USER_SUB_FACTORY),
{ provide: TitleStrategy, useClass: IsaTitleStrategy },
],
})
export class AppModule {}

View File

@@ -1,47 +1,82 @@
import { inject } from '@angular/core';
import { ActivatedRouteSnapshot, CanActivateFn, RouterStateSnapshot } from '@angular/router';
import { ApplicationService } from '@core/application';
import { Config } from '@core/config';
import { take } from 'rxjs/operators';
export const ActivateProcessIdGuard: CanActivateFn = async (
route: ActivatedRouteSnapshot,
state: RouterStateSnapshot,
) => {
const application = inject(ApplicationService);
const processIdStr = route.params.processId;
if (!processIdStr) {
return false;
}
const processId = Number(processIdStr);
// Check if Process already exists
const process = await application.getProcessById$(processId).pipe(take(1)).toPromise();
if (!process) {
application.createCustomerProcess(processId);
}
application.activateProcess(processId);
return true;
};
export const ActivateProcessIdWithConfigKeyGuard: (key: string) => CanActivateFn =
(key) => async (route: ActivatedRouteSnapshot, state: RouterStateSnapshot) => {
const application = inject(ApplicationService);
const config = inject(Config);
const processId = config.get(`process.ids.${key}`);
if (isNaN(processId)) {
return false;
}
application.activateProcess(processId);
return true;
};
import { inject } from '@angular/core';
import {
ActivatedRouteSnapshot,
CanActivateFn,
RouterStateSnapshot,
} from '@angular/router';
import { ApplicationService } from '@core/application';
import { Config } from '@core/config';
import { take } from 'rxjs/operators';
import z from 'zod';
export const ActivateProcessIdGuard: CanActivateFn = async (
route: ActivatedRouteSnapshot,
state: RouterStateSnapshot,
) => {
const application = inject(ApplicationService);
const processIdStr = route.params.processId;
if (!processIdStr) {
return false;
}
const processId = Number(processIdStr);
// Check if Process already exists
const process = await application
.getProcessById$(processId)
.pipe(take(1))
.toPromise();
if (!process) {
application.createProcess({
id: processId,
type: 'cart',
section: 'customer',
name: `Vorgang ${processId}`,
});
}
application.activateProcess(processId);
return true;
};
export const ActivateProcessIdWithConfigKeyGuard: (
key: string,
) => CanActivateFn =
(key) =>
async (route: ActivatedRouteSnapshot, state: RouterStateSnapshot) => {
const application = inject(ApplicationService);
const config = inject(Config);
const processId = config.get(`process.ids.${key}`, z.coerce.number());
if (typeof processId !== 'number' || isNaN(processId)) {
return false;
}
const processTitle = config.get(
`process.titles.${key}`,
z.string().default(key),
);
const process = await application
.getProcessById$(processId)
.pipe(take(1))
.toPromise();
if (!process) {
await application.createProcess({
id: processId,
type: key,
section: 'customer', // Not important anymore
name: processTitle,
});
}
application.activateProcess(processId);
return true;
};

View File

@@ -1,34 +1,34 @@
import { Injectable } from '@angular/core';
import { ActivatedRouteSnapshot, RouterStateSnapshot } from '@angular/router';
import { ApplicationService } from '@core/application';
import { Config } from '@core/config';
import { first } from 'rxjs/operators';
import { z } from 'zod';
@Injectable({ providedIn: 'root' })
export class CanActivateGoodsInGuard {
constructor(
private readonly _applicationService: ApplicationService,
private readonly _config: Config,
) {}
async canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) {
const pid = this._config.get('process.ids.goodsIn', z.number());
const process = await this._applicationService
.getProcessById$(pid)
.pipe(first())
.toPromise();
if (!process) {
await this._applicationService.createProcess({
id: this._config.get('process.ids.goodsIn'),
type: 'goods-in',
section: 'branch',
name: '',
});
}
this._applicationService.activateProcess(
this._config.get('process.ids.goodsIn'),
);
return true;
}
}
import { Injectable } from '@angular/core';
import { ActivatedRouteSnapshot, RouterStateSnapshot } from '@angular/router';
import { ApplicationService } from '@core/application';
import { Config } from '@core/config';
import { first } from 'rxjs/operators';
import { z } from 'zod';
@Injectable({ providedIn: 'root' })
export class CanActivateGoodsInGuard {
constructor(
private readonly _applicationService: ApplicationService,
private readonly _config: Config,
) {}
async canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) {
const pid = this._config.get('process.ids.goodsIn', z.number());
const process = await this._applicationService
.getProcessById$(pid)
.pipe(first())
.toPromise();
if (!process) {
await this._applicationService.createProcess({
id: this._config.get('process.ids.goodsIn'),
type: 'goods-in',
section: 'branch',
name: 'Abholfach',
});
}
this._applicationService.activateProcess(
this._config.get('process.ids.goodsIn'),
);
return true;
}
}

View File

@@ -8,24 +8,25 @@ import {
} from '@angular/common/http';
import { from, NEVER, Observable, throwError } from 'rxjs';
import { catchError, filter, mergeMap, takeUntil } from 'rxjs/operators';
import { LoginStrategy } from '@core/auth';
import { IsaLogProvider } from '../providers';
import { LogLevel } from '@core/logger';
import { AuthService, LoginStrategy } from '@core/auth';
import { injectOnline$ } from '../services/network-status.service';
import { logger } from '@isa/core/logging';
@Injectable()
export class HttpErrorInterceptor implements HttpInterceptor {
readonly offline$ = injectOnline$().pipe(filter((online) => !online));
readonly injector = inject(Injector);
constructor(private _isaLogProvider: IsaLogProvider) {}
#logger = logger(() => ({
'http-interceptor': 'HttpErrorInterceptor',
}));
#offline$ = injectOnline$().pipe(filter((online) => !online));
#injector = inject(Injector);
#auth = inject(AuthService);
intercept(
req: HttpRequest<any>,
next: HttpHandler,
): Observable<HttpEvent<any>> {
return next.handle(req).pipe(
takeUntil(this.offline$),
takeUntil(this.#offline$),
catchError((error: HttpErrorResponse, caught: any) =>
this.handleError(error),
),
@@ -33,18 +34,22 @@ export class HttpErrorInterceptor implements HttpInterceptor {
}
handleError(error: HttpErrorResponse): Observable<any> {
if (error.status === 401) {
const strategy = this.injector.get(LoginStrategy);
return this.#auth.initialized$.pipe(
mergeMap((initialized) => {
if (initialized && error.status === 401) {
const strategy = this.#injector.get(LoginStrategy);
return from(strategy.login('Sie sind nicht mehr angemeldet')).pipe(
mergeMap(() => NEVER),
);
}
return from(strategy.login('Sie sind nicht mehr angemeldet')).pipe(
mergeMap(() => NEVER),
);
}
if (!error.url.endsWith('/isa/logging')) {
this._isaLogProvider.log(LogLevel.ERROR, 'Http Error', error);
}
if (!error.url.endsWith('/isa/logging')) {
this.#logger.error('Http Error', error);
}
return throwError(error);
return throwError(() => error);
}),
);
}
}

View File

@@ -1,3 +0,0 @@
// start:ng42.barrel
export * from './preview.component';
// end:ng42.barrel

View File

@@ -1,3 +0,0 @@
:host {
@apply grid min-h-screen content-center justify-center;
}

View File

@@ -1,10 +0,0 @@
<h1>Platform: {{ platform | json }}</h1>
<br />
<h1>{{ appVersion }}</h1>
<br />
<h1>{{ userAgent }}</h1>
<br />
<h1>Navigator: {{ navigator | json }}</h1>
<br />
<br />
<h1>Device: {{ device }}</h1>

View File

@@ -1,56 +0,0 @@
import { Platform, PlatformModule } from '@angular/cdk/platform';
import { CommonModule } from '@angular/common';
import { Component } from '@angular/core';
import { BranchDTO } from '@generated/swagger/checkout-api';
import { BehaviorSubject } from 'rxjs';
@Component({
selector: 'app-preview',
templateUrl: 'preview.component.html',
styleUrls: ['preview.component.css'],
imports: [CommonModule, PlatformModule],
})
export class PreviewComponent {
selectedBranch$ = new BehaviorSubject<BranchDTO>({});
get appVersion() {
return 'App Version: ' + (window.navigator as any).appVersion;
}
get userAgent() {
return 'User Agent: ' + (window.navigator as any).userAgent;
}
get navigator() {
const nav = {};
for (const i in window.navigator) nav[i] = navigator[i];
return nav;
}
get platform() {
return this._platform;
}
get device() {
const isIpadNative = this._platform.IOS && !this._platform.SAFARI;
const isIpadMini6Native = window?.navigator?.userAgent?.includes('Macintosh') && !this._platform.SAFARI;
const isNative = isIpadNative || isIpadMini6Native;
const isPWA = this._platform.IOS && this._platform.SAFARI;
const isDesktop = !isNative && !isPWA;
if (isNative) {
if (isIpadMini6Native) {
return 'IPAD mini 6 Native App';
} else if (isIpadNative) {
return 'IPAD mini 2 Native App or IPAD mini 5 Native App';
}
} else if (isPWA) {
return 'IPAD Safari PWA';
} else if (isDesktop) return 'Desktop or Macintosh';
}
constructor(private readonly _platform: Platform) {}
setNewBranch(branch: BranchDTO) {
this.selectedBranch$.next(branch);
}
}

View File

@@ -1,4 +1,2 @@
// start:ng42.barrel
export * from './process-id.resolver';
export * from './section.resolver';
// end:ng42.barrel
export * from './process-id.resolver';
export * from './section.resolver';

View File

@@ -1,85 +1,85 @@
{
"title": "ISA - Feature",
"silentRefresh": {
"interval": 300000
},
"@cdn/product-image": {
"url": "https://produktbilder.paragon-data.net"
},
"@core/auth": {
"issuer": "https://sso-test.paragon-data.de",
"clientId": "hug-isa",
"responseType": "id_token token",
"oidc": true,
"scope": "openid profile cmf_user isa-isa-webapi isa-checkout-webapi isa-cat-webapi isa-ava-webapi isa-crm-webapi isa-review-webapi isa-kpi-webapi isa-oms-webapi isa-nbo-webapi isa-print-webapi eis-service isa-inv-webapi isa-wws-webapi"
},
"@core/logger": {
"logLevel": "debug"
},
"@domain/checkout": {
"olaExpiration": "5m"
},
"@swagger/isa": {
"rootUrl": "https://isa-feature.paragon-data.net/isa/v1"
},
"@swagger/cat": {
"rootUrl": "https://isa-test.paragon-data.net/catsearch/v6"
},
"@swagger/av": {
"rootUrl": "https://isa-test.paragon-data.net/ava/v6"
},
"@swagger/checkout": {
"rootUrl": "https://isa-feature.paragon-data.net/checkout/v6"
},
"@swagger/crm": {
"rootUrl": "https://isa-feature.paragon-data.net/crm/v6"
},
"@swagger/oms": {
"rootUrl": "https://isa-feature.paragon-data.net/oms/v6"
},
"@swagger/print": {
"rootUrl": "https://isa-feature.paragon-data.net/print/v1"
},
"@swagger/eis": {
"rootUrl": "https://filialinformationsystem-test.paragon-systems.de/eiswebapi/v1"
},
"@swagger/remi": {
"rootUrl": "https://isa-feature.paragon-data.net/inv/v6"
},
"@swagger/wws": {
"rootUrl": "https://isa-test.paragon-data.net/wws/v1"
},
"hubs": {
"notifications": {
"url": "https://isa-feature.paragon-data.net/isa/v1/rt",
"enableAutomaticReconnect": false,
"httpOptions": {
"transport": 1,
"logMessageContent": true,
"skipNegotiation": true
}
}
},
"process": {
"ids": {
"goodsOut": 1000,
"goodsIn": 2000,
"taskCalendar": 3000,
"remission": 4000,
"packageInspection": 5000,
"assortment": 6000,
"pickupShelf": 7000
}
},
"checkForUpdates": 3600000,
"licence": {
"scandit": "Ae8F2Wx2RMq5Lvn7UUAlWzVFZTt2+ubMAF8XtDpmPlNkBeG/LWs1M7AbgDW0LQqYLnszClEENaEHS56/6Ts2vrJ1Ux03CXUjK3jUvZpF5OchXR1CpnmpepJ6WxPCd7LMVHUGG1BbwPLDTFjP3y8uT0caTSmmGrYQWAs4CZcEF+ZBabP0z7vfm+hCZF/ebj9qqCJZcW8nH/n19hohshllzYBjFXjh87P2lIh1s6yZS3OaQWWXo/o0AKdxx7T6CVyR0/G5zq6uYJWf6rs3euUBEhpzOZHbHZK86Lvy2AVBEyVkkcttlDW1J2fA4l1W1JV/Xibz8AQV6kG482EpGF42KEoK48paZgX3e1AQsqUtmqzw294dcP4zMVstnw5/WrwKKi/5E/nOOJT2txYP1ZufIjPrwNFsqTlv7xCQlHjMzFGYwT816yD5qLRLbwOtjrkUPXNZLZ06T4upvWwJDmm8XgdeoDqMjHdcO4lwji1bl9EiIYJ/2qnsk9yZ2FqSaHzn4cbiL0f5u2HFlNAP0GUujGRlthGhHi6o4dFU+WAxKsFMKVt+SfoQUazNKHFVQgiAklTIZxIc/HUVzRvOLMxf+wFDerraBtcqGJg+g/5mrWYqeDBGhCBHtKiYf6244IJ4afzNTiH1/30SJcRzXwbEa3A7q1fJTx9/nLTOfVPrJKBQs7f/OQs2dA7LDCel8mzXdbjvsNQaeU5+iCIAq6zbTNKy1xT8wwj+VZrQmtNJs+qeznD+u29nCM24h8xCmRpvNPo4/Mww/lrTNrrNwLBSn1pMIwsH7yS9hH0v0oNAM3A6bVtk1D9qEkbyw+xZa+MZGpMP0D0CdcsqHalPcm5r/Ik="
},
"gender": {
"0": "Keine Anrede",
"1": "Enby",
"2": "Herr",
"4": "Frau"
},
"@shared/icon": "/assets/icons.json"
}
{
"title": "ISA - Feature",
"silentRefresh": {
"interval": 300000
},
"@cdn/product-image": {
"url": "https://produktbilder.paragon-data.net"
},
"@core/auth": {
"issuer": "https://sso-test.paragon-data.de",
"clientId": "hug-isa",
"responseType": "id_token token",
"oidc": true,
"scope": "openid profile cmf_user isa-isa-webapi isa-checkout-webapi isa-cat-webapi isa-ava-webapi isa-crm-webapi isa-review-webapi isa-kpi-webapi isa-oms-webapi isa-nbo-webapi isa-print-webapi eis-service isa-inv-webapi isa-wws-webapi"
},
"@core/logger": {
"logLevel": "debug"
},
"@domain/checkout": {
"olaExpiration": "5m"
},
"@swagger/isa": {
"rootUrl": "https://isa-test.paragon-data.net/isa/v1"
},
"@swagger/cat": {
"rootUrl": "https://isa-test.paragon-data.net/catsearch/v6"
},
"@swagger/av": {
"rootUrl": "https://isa-test.paragon-data.net/ava/v6"
},
"@swagger/checkout": {
"rootUrl": "https://isa-feature.paragon-data.net/checkout/v6"
},
"@swagger/crm": {
"rootUrl": "https://isa-feature.paragon-data.net/crm/v6"
},
"@swagger/oms": {
"rootUrl": "https://isa-feature.paragon-data.net/oms/v6"
},
"@swagger/print": {
"rootUrl": "https://isa-feature.paragon-data.net/print/v1"
},
"@swagger/eis": {
"rootUrl": "https://filialinformationsystem-test.paragon-systems.de/eiswebapi/v1"
},
"@swagger/remi": {
"rootUrl": "https://isa-feature.paragon-data.net/inv/v6"
},
"@swagger/wws": {
"rootUrl": "https://isa-test.paragon-data.net/wws/v1"
},
"hubs": {
"notifications": {
"url": "https://isa-feature.paragon-data.net/isa/v1/rt",
"enableAutomaticReconnect": false,
"httpOptions": {
"transport": 1,
"logMessageContent": true,
"skipNegotiation": true
}
}
},
"process": {
"ids": {
"goodsOut": 1000,
"goodsIn": 2000,
"taskCalendar": 3000,
"remission": 4000,
"packageInspection": 5000,
"assortment": 6000,
"pickupShelf": 7000
}
},
"checkForUpdates": 3600000,
"licence": {
"scandit": "Ae8F2Wx2RMq5Lvn7UUAlWzVFZTt2+ubMAF8XtDpmPlNkBeG/LWs1M7AbgDW0LQqYLnszClEENaEHS56/6Ts2vrJ1Ux03CXUjK3jUvZpF5OchXR1CpnmpepJ6WxPCd7LMVHUGG1BbwPLDTFjP3y8uT0caTSmmGrYQWAs4CZcEF+ZBabP0z7vfm+hCZF/ebj9qqCJZcW8nH/n19hohshllzYBjFXjh87P2lIh1s6yZS3OaQWWXo/o0AKdxx7T6CVyR0/G5zq6uYJWf6rs3euUBEhpzOZHbHZK86Lvy2AVBEyVkkcttlDW1J2fA4l1W1JV/Xibz8AQV6kG482EpGF42KEoK48paZgX3e1AQsqUtmqzw294dcP4zMVstnw5/WrwKKi/5E/nOOJT2txYP1ZufIjPrwNFsqTlv7xCQlHjMzFGYwT816yD5qLRLbwOtjrkUPXNZLZ06T4upvWwJDmm8XgdeoDqMjHdcO4lwji1bl9EiIYJ/2qnsk9yZ2FqSaHzn4cbiL0f5u2HFlNAP0GUujGRlthGhHi6o4dFU+WAxKsFMKVt+SfoQUazNKHFVQgiAklTIZxIc/HUVzRvOLMxf+wFDerraBtcqGJg+g/5mrWYqeDBGhCBHtKiYf6244IJ4afzNTiH1/30SJcRzXwbEa3A7q1fJTx9/nLTOfVPrJKBQs7f/OQs2dA7LDCel8mzXdbjvsNQaeU5+iCIAq6zbTNKy1xT8wwj+VZrQmtNJs+qeznD+u29nCM24h8xCmRpvNPo4/Mww/lrTNrrNwLBSn1pMIwsH7yS9hH0v0oNAM3A6bVtk1D9qEkbyw+xZa+MZGpMP0D0CdcsqHalPcm5r/Ik="
},
"gender": {
"0": "Keine Anrede",
"1": "Enby",
"2": "Herr",
"4": "Frau"
},
"@shared/icon": "/assets/icons.json"
}

View File

@@ -1,87 +1,86 @@
{
"title": "ISA - Local",
"silentRefresh": {
"interval": 300000
},
"debug": true,
"dev-scanner": true,
"@cdn/product-image": {
"url": "https://produktbilder.paragon-data.net"
},
"@core/auth": {
"issuer": "https://sso-test.paragon-data.de",
"clientId": "isa-client",
"responseType": "code",
"scope": "openid profile cmf_user isa-isa-webapi isa-checkout-webapi isa-cat-webapi isa-ava-webapi isa-crm-webapi isa-review-webapi isa-kpi-webapi isa-oms-webapi isa-nbo-webapi isa-print-webapi eis-service isa-inv-webapi isa-wws-webapi",
"showDebugInformation": true
},
"@core/logger": {
"logLevel": "debug"
},
"@swagger/isa": {
"rootUrl": "https://isa-test.paragon-data.net/isa/v1"
},
"@swagger/cat": {
"rootUrl": "https://isa-test.paragon-data.net/catsearch/v6"
},
"@swagger/av": {
"rootUrl": "https://isa-test.paragon-data.net/ava/v6"
},
"@swagger/checkout": {
"rootUrl": "https://isa-test.paragon-data.net/checkout/v6"
},
"@swagger/crm": {
"rootUrl": "https://isa-test.paragon-data.net/crm/v6"
},
"@swagger/oms": {
"rootUrl": "https://isa-test.paragon-data.net/oms/v6"
},
"@swagger/print": {
"rootUrl": "https://isa-test.paragon-data.net/print/v1"
},
"@swagger/eis": {
"rootUrl": "https://filialinformationsystem-test.paragon-systems.de/eiswebapi/v1"
},
"@swagger/remi": {
"rootUrl": "https://isa-test.paragon-data.net/inv/v6"
},
"@swagger/wws": {
"rootUrl": "https://isa-test.paragon-data.net/wws/v1"
},
"@domain/checkout": {
"olaExpiration": "5m"
},
"hubs": {
"notifications": {
"url": "https://isa-test.paragon-data.net/isa/v1/rt",
"enableAutomaticReconnect": false,
"httpOptions": {
"transport": 1,
"logMessageContent": true,
"skipNegotiation": true
}
}
},
"process": {
"ids": {
"goodsOut": 1000,
"goodsIn": 2000,
"taskCalendar": 3000,
"remission": 4000,
"packageInspection": 5000,
"assortment": 6000,
"pickupShelf": 7000
}
},
"checkForUpdates": 3600000,
"licence": {
"scandit": "Ae8F2Wx2RMq5Lvn7UUAlWzVFZTt2+ubMAF8XtDpmPlNkBeG/LWs1M7AbgDW0LQqYLnszClEENaEHS56/6Ts2vrJ1Ux03CXUjK3jUvZpF5OchXR1CpnmpepJ6WxPCd7LMVHUGG1BbwPLDTFjP3y8uT0caTSmmGrYQWAs4CZcEF+ZBabP0z7vfm+hCZF/ebj9qqCJZcW8nH/n19hohshllzYBjFXjh87P2lIh1s6yZS3OaQWWXo/o0AKdxx7T6CVyR0/G5zq6uYJWf6rs3euUBEhpzOZHbHZK86Lvy2AVBEyVkkcttlDW1J2fA4l1W1JV/Xibz8AQV6kG482EpGF42KEoK48paZgX3e1AQsqUtmqzw294dcP4zMVstnw5/WrwKKi/5E/nOOJT2txYP1ZufIjPrwNFsqTlv7xCQlHjMzFGYwT816yD5qLRLbwOtjrkUPXNZLZ06T4upvWwJDmm8XgdeoDqMjHdcO4lwji1bl9EiIYJ/2qnsk9yZ2FqSaHzn4cbiL0f5u2HFlNAP0GUujGRlthGhHi6o4dFU+WAxKsFMKVt+SfoQUazNKHFVQgiAklTIZxIc/HUVzRvOLMxf+wFDerraBtcqGJg+g/5mrWYqeDBGhCBHtKiYf6244IJ4afzNTiH1/30SJcRzXwbEa3A7q1fJTx9/nLTOfVPrJKBQs7f/OQs2dA7LDCel8mzXdbjvsNQaeU5+iCIAq6zbTNKy1xT8wwj+VZrQmtNJs+qeznD+u29nCM24h8xCmRpvNPo4/Mww/lrTNrrNwLBSn1pMIwsH7yS9hH0v0oNAM3A6bVtk1D9qEkbyw+xZa+MZGpMP0D0CdcsqHalPcm5r/Ik="
},
"gender": {
"0": "Keine Anrede",
"1": "Enby",
"2": "Herr",
"4": "Frau"
},
"@shared/icon": "/assets/icons.json"
}
{
"title": "ISA - Local",
"silentRefresh": {
"interval": 300000
},
"debug": true,
"dev-scanner": true,
"@cdn/product-image": {
"url": "https://produktbilder.paragon-data.net"
},
"@core/auth": {
"issuer": "https://sso-test.paragon-data.de",
"clientId": "isa-client",
"responseType": "code",
"scope": "openid profile cmf_user isa-isa-webapi isa-checkout-webapi isa-cat-webapi isa-ava-webapi isa-crm-webapi isa-review-webapi isa-kpi-webapi isa-oms-webapi isa-nbo-webapi isa-print-webapi eis-service isa-inv-webapi isa-wws-webapi",
"showDebugInformation": true
},
"@core/logger": {
"logLevel": "debug"
},
"@swagger/isa": {
"rootUrl": "https://isa-test.paragon-data.net/isa/v1"
},
"@swagger/cat": {
"rootUrl": "https://isa-test.paragon-data.net/catsearch/v6"
},
"@swagger/av": {
"rootUrl": "https://isa-test.paragon-data.net/ava/v6"
},
"@swagger/checkout": {
"rootUrl": "https://isa-test.paragon-data.net/checkout/v6"
},
"@swagger/crm": {
"rootUrl": "https://isa-test.paragon-data.net/crm/v6"
},
"@swagger/oms": {
"rootUrl": "https://isa-test.paragon-data.net/oms/v6"
},
"@swagger/print": {
"rootUrl": "https://isa-test.paragon-data.net/print/v1"
},
"@swagger/eis": {
"rootUrl": "https://filialinformationsystem-test.paragon-systems.de/eiswebapi/v1"
},
"@swagger/remi": {
"rootUrl": "https://isa-test.paragon-data.net/inv/v6"
},
"@swagger/wws": {
"rootUrl": "https://isa-test.paragon-data.net/wws/v1"
},
"@domain/checkout": {
"olaExpiration": "5m"
},
"hubs": {
"notifications": {
"url": "https://isa-test.paragon-data.net/isa/v1/rt",
"enableAutomaticReconnect": false,
"httpOptions": {
"transport": 1,
"logMessageContent": true,
"skipNegotiation": true
}
}
},
"process": {
"ids": {
"goodsOut": 1000,
"goodsIn": 2000,
"taskCalendar": 3000,
"packageInspection": 5000,
"assortment": 6000,
"pickupShelf": 2000
}
},
"checkForUpdates": 3600000,
"licence": {
"scandit": "Ae8F2Wx2RMq5Lvn7UUAlWzVFZTt2+ubMAF8XtDpmPlNkBeG/LWs1M7AbgDW0LQqYLnszClEENaEHS56/6Ts2vrJ1Ux03CXUjK3jUvZpF5OchXR1CpnmpepJ6WxPCd7LMVHUGG1BbwPLDTFjP3y8uT0caTSmmGrYQWAs4CZcEF+ZBabP0z7vfm+hCZF/ebj9qqCJZcW8nH/n19hohshllzYBjFXjh87P2lIh1s6yZS3OaQWWXo/o0AKdxx7T6CVyR0/G5zq6uYJWf6rs3euUBEhpzOZHbHZK86Lvy2AVBEyVkkcttlDW1J2fA4l1W1JV/Xibz8AQV6kG482EpGF42KEoK48paZgX3e1AQsqUtmqzw294dcP4zMVstnw5/WrwKKi/5E/nOOJT2txYP1ZufIjPrwNFsqTlv7xCQlHjMzFGYwT816yD5qLRLbwOtjrkUPXNZLZ06T4upvWwJDmm8XgdeoDqMjHdcO4lwji1bl9EiIYJ/2qnsk9yZ2FqSaHzn4cbiL0f5u2HFlNAP0GUujGRlthGhHi6o4dFU+WAxKsFMKVt+SfoQUazNKHFVQgiAklTIZxIc/HUVzRvOLMxf+wFDerraBtcqGJg+g/5mrWYqeDBGhCBHtKiYf6244IJ4afzNTiH1/30SJcRzXwbEa3A7q1fJTx9/nLTOfVPrJKBQs7f/OQs2dA7LDCel8mzXdbjvsNQaeU5+iCIAq6zbTNKy1xT8wwj+VZrQmtNJs+qeznD+u29nCM24h8xCmRpvNPo4/Mww/lrTNrrNwLBSn1pMIwsH7yS9hH0v0oNAM3A6bVtk1D9qEkbyw+xZa+MZGpMP0D0CdcsqHalPcm5r/Ik="
},
"gender": {
"0": "Keine Anrede",
"1": "Enby",
"2": "Herr",
"4": "Frau"
},
"@shared/icon": "/assets/icons.json"
}

View File

@@ -1,174 +1,196 @@
import { Injectable } from '@angular/core';
import { Store } from '@ngrx/store';
import { BranchDTO } from '@generated/swagger/checkout-api';
import { isBoolean, isNumber } from '@utils/common';
import { BehaviorSubject, Observable } from 'rxjs';
import { first, map, switchMap } from 'rxjs/operators';
import { ApplicationProcess } from './defs';
import {
removeProcess,
selectSection,
selectProcesses,
setSection,
addProcess,
setActivatedProcess,
selectActivatedProcess,
patchProcess,
patchProcessData,
selectTitle,
setTitle,
} from './store';
@Injectable()
export class ApplicationService {
private activatedProcessIdSubject = new BehaviorSubject<number>(undefined);
get activatedProcessId() {
return this.activatedProcessIdSubject.value;
}
get activatedProcessId$() {
return this.activatedProcessIdSubject.asObservable();
}
constructor(private store: Store) {}
getProcesses$(section?: 'customer' | 'branch') {
const processes$ = this.store.select(selectProcesses);
return processes$.pipe(
map((processes) => processes.filter((process) => (section ? process.section === section : true))),
);
}
getProcessById$(processId: number): Observable<ApplicationProcess> {
return this.getProcesses$().pipe(map((processes) => processes.find((process) => process.id === processId)));
}
getSection$() {
return this.store.select(selectSection);
}
getTitle$() {
return this.getSection$().pipe(
map((section) => {
return section === 'customer' ? 'Kundenbereich' : 'Filialbereich';
}),
);
}
/** @deprecated */
getActivatedProcessId$() {
return this.store.select(selectActivatedProcess).pipe(map((process) => process?.id));
}
activateProcess(activatedProcessId: number) {
this.store.dispatch(setActivatedProcess({ activatedProcessId }));
this.activatedProcessIdSubject.next(activatedProcessId);
}
removeProcess(processId: number) {
this.store.dispatch(removeProcess({ processId }));
}
patchProcess(processId: number, changes: Partial<ApplicationProcess>) {
this.store.dispatch(patchProcess({ processId, changes }));
}
patchProcessData(processId: number, data: Record<string, any>) {
this.store.dispatch(patchProcessData({ processId, data }));
}
getSelectedBranch$(processId?: number): Observable<BranchDTO> {
if (!processId) {
return this.activatedProcessId$.pipe(
switchMap((processId) => this.getProcessById$(processId).pipe(map((process) => process?.data?.selectedBranch))),
);
}
return this.getProcessById$(processId).pipe(map((process) => process?.data?.selectedBranch));
}
readonly REGEX_PROCESS_NAME = /^Vorgang \d+$/;
async createCustomerProcess(processId?: number): Promise<ApplicationProcess> {
const processes = await this.getProcesses$('customer').pipe(first()).toPromise();
const processIds = processes.filter((x) => this.REGEX_PROCESS_NAME.test(x.name)).map((x) => +x.name.split(' ')[1]);
const maxId = processIds.length > 0 ? Math.max(...processIds) : 0;
const process: ApplicationProcess = {
id: processId ?? Date.now(),
type: 'cart',
name: `Vorgang ${maxId + 1}`,
section: 'customer',
closeable: true,
};
await this.createProcess(process);
return process;
}
async createProcess(process: ApplicationProcess) {
const existingProcess = await this.getProcessById$(process?.id).pipe(first()).toPromise();
if (existingProcess?.id === process?.id) {
throw new Error('Process Id existiert bereits');
}
if (!isNumber(process.id)) {
throw new Error('Process Id nicht gesetzt');
}
if (!isBoolean(process.closeable)) {
process.closeable = true;
}
if (!isBoolean(process.confirmClosing)) {
process.confirmClosing = true;
}
process.created = this._createTimestamp();
process.activated = 0;
this.store.dispatch(addProcess({ process }));
}
setSection(section: 'customer' | 'branch') {
this.store.dispatch(setSection({ section }));
}
getLastActivatedProcessWithSectionAndType$(
section: 'customer' | 'branch',
type: string,
): Observable<ApplicationProcess> {
return this.getProcesses$(section).pipe(
map((processes) =>
processes
?.filter((process) => process.type === type)
?.reduce((latest, current) => {
if (!latest) {
return current;
}
return latest?.activated > current?.activated ? latest : current;
}, undefined),
),
);
}
getLastActivatedProcessWithSection$(section: 'customer' | 'branch'): Observable<ApplicationProcess> {
return this.getProcesses$(section).pipe(
map((processes) =>
processes?.reduce((latest, current) => {
if (!latest) {
return current;
}
return latest?.activated > current?.activated ? latest : current;
}, undefined),
),
);
}
private _createTimestamp() {
return Date.now();
}
}
import { Injectable } from '@angular/core';
import { Store } from '@ngrx/store';
import { BranchDTO } from '@generated/swagger/checkout-api';
import { isBoolean, isNumber } from '@utils/common';
import { BehaviorSubject, Observable } from 'rxjs';
import { first, map, switchMap } from 'rxjs/operators';
import { ApplicationProcess } from './defs';
import {
removeProcess,
selectSection,
selectProcesses,
setSection,
addProcess,
setActivatedProcess,
selectActivatedProcess,
patchProcess,
patchProcessData,
selectTitle,
setTitle,
} from './store';
@Injectable()
export class ApplicationService {
private activatedProcessIdSubject = new BehaviorSubject<number>(undefined);
get activatedProcessId() {
return this.activatedProcessIdSubject.value;
}
get activatedProcessId$() {
return this.activatedProcessIdSubject.asObservable();
}
constructor(private store: Store) {}
getProcesses$(section?: 'customer' | 'branch') {
const processes$ = this.store.select(selectProcesses);
return processes$.pipe(
map((processes) =>
processes.filter((process) =>
section ? process.section === section : true,
),
),
);
}
getProcessById$(processId: number): Observable<ApplicationProcess> {
return this.getProcesses$().pipe(
map((processes) => processes.find((process) => process.id === processId)),
);
}
getSection$() {
return this.store.select(selectSection);
}
getTitle$() {
return this.getSection$().pipe(
map((section) => {
return section === 'customer' ? 'Kundenbereich' : 'Filialbereich';
}),
);
}
/** @deprecated */
getActivatedProcessId$() {
return this.store
.select(selectActivatedProcess)
.pipe(map((process) => process?.id));
}
activateProcess(activatedProcessId: number) {
this.store.dispatch(setActivatedProcess({ activatedProcessId }));
this.activatedProcessIdSubject.next(activatedProcessId);
}
removeProcess(processId: number) {
this.store.dispatch(removeProcess({ processId }));
}
patchProcess(processId: number, changes: Partial<ApplicationProcess>) {
this.store.dispatch(patchProcess({ processId, changes }));
}
patchProcessData(processId: number, data: Record<string, any>) {
this.store.dispatch(patchProcessData({ processId, data }));
}
getSelectedBranch$(processId?: number): Observable<BranchDTO> {
if (!processId) {
return this.activatedProcessId$.pipe(
switchMap((processId) =>
this.getProcessById$(processId).pipe(
map((process) => process?.data?.selectedBranch),
),
),
);
}
return this.getProcessById$(processId).pipe(
map((process) => process?.data?.selectedBranch),
);
}
readonly REGEX_PROCESS_NAME = /^Vorgang \d+$/;
async createCustomerProcess(processId?: number): Promise<ApplicationProcess> {
const processes = await this.getProcesses$('customer')
.pipe(first())
.toPromise();
const processIds = processes
.filter((x) => this.REGEX_PROCESS_NAME.test(x.name))
.map((x) => +x.name.split(' ')[1]);
const maxId = processIds.length > 0 ? Math.max(...processIds) : 0;
const process: ApplicationProcess = {
id: processId ?? Date.now(),
type: 'cart',
name: `Vorgang ${maxId + 1}`,
section: 'customer',
closeable: true,
};
await this.createProcess(process);
return process;
}
async createProcess(process: ApplicationProcess) {
const existingProcess = await this.getProcessById$(process?.id)
.pipe(first())
.toPromise();
if (existingProcess?.id === process?.id) {
throw new Error('Process Id existiert bereits');
}
if (!isNumber(process.id)) {
throw new Error('Process Id nicht gesetzt');
}
if (!isBoolean(process.closeable)) {
process.closeable = true;
}
if (!isBoolean(process.confirmClosing)) {
process.confirmClosing = true;
}
process.created = this._createTimestamp();
process.activated = 0;
this.store.dispatch(addProcess({ process }));
}
setSection(section: 'customer' | 'branch') {
this.store.dispatch(setSection({ section }));
}
getLastActivatedProcessWithSectionAndType$(
section: 'customer' | 'branch',
type: string,
): Observable<ApplicationProcess> {
return this.getProcesses$(section).pipe(
map((processes) =>
processes
?.filter((process) => process.type === type)
?.reduce((latest, current) => {
if (!latest) {
return current;
}
return latest?.activated > current?.activated ? latest : current;
}, undefined),
),
);
}
getLastActivatedProcessWithSection$(
section: 'customer' | 'branch',
): Observable<ApplicationProcess> {
return this.getProcesses$(section).pipe(
map((processes) =>
processes?.reduce((latest, current) => {
if (!latest) {
return current;
}
return latest?.activated > current?.activated ? latest : current;
}, undefined),
),
);
}
private _createTimestamp() {
return Date.now();
}
}

View File

@@ -5,6 +5,8 @@ import { isNullOrUndefined } from '@utils/common';
import { AuthConfig, OAuthService } from 'angular-oauth2-oidc';
import { JwksValidationHandler } from 'angular-oauth2-oidc-jwks';
import { BehaviorSubject } from 'rxjs';
import { logger } from '@isa/core/logging';
import { Router } from '@angular/router';
/**
* Storage key for the URL to redirect to after login
@@ -15,9 +17,17 @@ const REDIRECT_URL_KEY = 'auth_redirect_url';
providedIn: 'root',
})
export class AuthService {
private readonly _initialized = new BehaviorSubject<boolean>(false);
#logger = logger(() => ({ service: 'AuthService' }));
#router = inject(Router);
#initialized = new BehaviorSubject<boolean>(false);
get initialized$() {
return this._initialized.asObservable();
return this.#initialized.asObservable();
}
#authenticated = new BehaviorSubject<boolean>(false);
get authenticated$() {
return this.#authenticated.asObservable();
}
private _authConfig: AuthConfig;
@@ -27,16 +37,21 @@ export class AuthService {
) {
this._oAuthService.events?.subscribe((event) => {
if (event.type === 'token_received') {
console.log(
'SSO Token Expiration:',
new Date(this._oAuthService.getAccessTokenExpiration()),
);
this.#logger.info('SSO token received', () => ({
tokenExpiration: new Date(
this._oAuthService.getAccessTokenExpiration(),
).toISOString(),
}));
// Handle redirect after successful authentication
setTimeout(() => {
const redirectUrl = this._getAndClearRedirectUrl();
if (redirectUrl) {
window.location.href = redirectUrl;
this.#logger.debug('Redirecting after authentication', () => ({
redirectUrl,
}));
this.#router.navigateByUrl(redirectUrl);
}
}, 100);
}
@@ -44,50 +59,72 @@ export class AuthService {
}
async init() {
if (this._initialized.getValue()) {
if (this.#initialized.getValue()) {
this.#logger.error(
'AuthService initialization attempted twice',
new Error('Already initialized'),
);
throw new Error('AuthService is already initialized');
}
this.#logger.info('Initializing AuthService');
this._authConfig = this._config.get('@core/auth');
this.#logger.debug('Auth config loaded', () => ({
issuer: this._authConfig.issuer,
clientId: this._authConfig.clientId,
scope: this._authConfig.scope,
}));
this._authConfig.redirectUri = window.location.origin;
this._authConfig.silentRefreshRedirectUri =
window.location.origin + '/silent-refresh.html';
this._authConfig.useSilentRefresh = true;
this.#logger.debug('Auth URIs configured', () => ({
redirectUri: this._authConfig.redirectUri,
silentRefreshRedirectUri: this._authConfig.silentRefreshRedirectUri,
}));
this._oAuthService.configure(this._authConfig);
this._oAuthService.tokenValidationHandler = new JwksValidationHandler();
this.#logger.debug('Setting up automatic silent refresh');
this._oAuthService.setupAutomaticSilentRefresh();
await this._oAuthService.loadDiscoveryDocumentAndTryLogin();
this.#logger.debug('Loading discovery document and attempting login');
const authenticated =
await this._oAuthService.loadDiscoveryDocumentAndTryLogin();
if (!this._oAuthService.getAccessToken()) {
throw new Error('No access token. User is not authenticated.');
}
this.#authenticated.next(authenticated);
this.#logger.info('AuthService initialized', () => ({ authenticated }));
this._initialized.next(true);
this.#initialized.next(true);
return authenticated;
}
isAuthenticated() {
return this.isIdTokenValid();
return this.#authenticated.getValue();
}
isIdTokenValid() {
console.log(
'ID Token Expiration:',
new Date(this._oAuthService.getIdTokenExpiration()),
);
return this._oAuthService.hasValidIdToken();
const expiration = new Date(this._oAuthService.getIdTokenExpiration());
const isValid = this._oAuthService.hasValidIdToken();
this.#logger.debug('ID token validation check', () => ({
expiration: expiration.toISOString(),
isValid,
}));
return isValid;
}
isAccessTokenValid() {
console.log(
'ACCESS Token Expiration:',
new Date(this._oAuthService.getAccessTokenExpiration()),
);
return this._oAuthService.hasValidAccessToken();
const expiration = new Date(this._oAuthService.getAccessTokenExpiration());
const isValid = this._oAuthService.hasValidAccessToken();
this.#logger.debug('Access token validation check', () => ({
expiration: expiration.toISOString(),
isValid,
}));
return isValid;
}
getToken() {
@@ -111,6 +148,7 @@ export class AuthService {
if (isNullOrUndefined(token)) {
return null;
}
const base64Url = token.split('.')[1];
const base64 = base64Url.replace(/-/g, '+').replace(/_/g, '/');
@@ -135,18 +173,22 @@ export class AuthService {
}
login() {
this.#logger.info('Initiating login flow');
this._saveRedirectUrl();
this._oAuthService.initLoginFlow();
}
setKeyCardToken(token: string) {
this.#logger.debug('Setting keycard token');
this._oAuthService.customQueryParams = {
temp_token: token,
};
}
async logout() {
this.#logger.info('Initiating logout');
await this._oAuthService.revokeTokenAndLogout();
this.#logger.info('Logout completed');
}
hasRole(role: string | string[]) {
@@ -163,16 +205,20 @@ export class AuthService {
async refresh() {
try {
this.#logger.debug('Refreshing authentication token');
if (
this._authConfig.responseType.includes('code') &&
this._authConfig.scope.includes('offline_access')
) {
await this._oAuthService.refreshToken();
this.#logger.info('Token refreshed using refresh token');
} else {
await this._oAuthService.silentRefresh();
this.#logger.info('Token refreshed using silent refresh');
}
} catch (error) {
console.error(error);
this.#logger.error('Token refresh failed', error as Error);
}
}
}

View File

@@ -3,31 +3,49 @@ import { ActionHandler } from './action-handler.interface';
import { CommandService } from './command.service';
import { FEATURE_ACTION_HANDLERS, ROOT_ACTION_HANDLERS } from './tokens';
export function provideActionHandlers(actionHandlers: Type<ActionHandler>[]): Provider[] {
export function provideActionHandlers(
actionHandlers: Type<ActionHandler>[],
): Provider[] {
return [
CommandService,
actionHandlers.map((handler) => ({ provide: FEATURE_ACTION_HANDLERS, useClass: handler, multi: true })),
actionHandlers.map((handler) => ({
provide: FEATURE_ACTION_HANDLERS,
useClass: handler,
multi: true,
})),
];
}
@NgModule({})
export class CoreCommandModule {
static forRoot(actionHandlers: Type<ActionHandler>[]): ModuleWithProviders<CoreCommandModule> {
static forRoot(
actionHandlers: Type<ActionHandler>[],
): ModuleWithProviders<CoreCommandModule> {
return {
ngModule: CoreCommandModule,
providers: [
CommandService,
actionHandlers.map((handler) => ({ provide: ROOT_ACTION_HANDLERS, useClass: handler, multi: true })),
actionHandlers.map((handler) => ({
provide: ROOT_ACTION_HANDLERS,
useClass: handler,
multi: true,
})),
],
};
}
static forChild(actionHandlers: Type<ActionHandler>[]): ModuleWithProviders<CoreCommandModule> {
static forChild(
actionHandlers: Type<ActionHandler>[],
): ModuleWithProviders<CoreCommandModule> {
return {
ngModule: CoreCommandModule,
providers: [
CommandService,
actionHandlers.map((handler) => ({ provide: FEATURE_ACTION_HANDLERS, useClass: handler, multi: true })),
actionHandlers.map((handler) => ({
provide: FEATURE_ACTION_HANDLERS,
useClass: handler,
multi: true,
})),
],
};
}

View File

@@ -1,43 +1,54 @@
import { Injectable, Injector, Optional, SkipSelf } from '@angular/core';
import { ActionHandler } from './action-handler.interface';
import { FEATURE_ACTION_HANDLERS, ROOT_ACTION_HANDLERS } from './tokens';
@Injectable()
export class CommandService {
constructor(
private injector: Injector,
@Optional() @SkipSelf() private _parent: CommandService,
) {}
async handleCommand<T>(command: string, data?: T): Promise<T> {
const actions = this.getActions(command);
for (const action of actions) {
const handler = this.getActionHandler(action);
if (!handler) {
console.error('CommandService.handleCommand', 'Action Handler does not exist', { action });
throw new Error('Action Handler does not exist');
}
data = await handler.handler(data, this);
}
return data;
}
getActions(command: string) {
return command?.split('|') || [];
}
getActionHandler(action: string): ActionHandler | undefined {
const featureActionHandlers: ActionHandler[] = this.injector.get(FEATURE_ACTION_HANDLERS, []);
const rootActionHandlers: ActionHandler[] = this.injector.get(ROOT_ACTION_HANDLERS, []);
let handler = [...featureActionHandlers, ...rootActionHandlers].find((handler) => handler.action === action);
if (this._parent && !handler) {
handler = this._parent.getActionHandler(action);
}
return handler;
}
}
import { Injectable, Injector, Optional, SkipSelf } from '@angular/core';
import { ActionHandler } from './action-handler.interface';
import { FEATURE_ACTION_HANDLERS, ROOT_ACTION_HANDLERS } from './tokens';
@Injectable()
export class CommandService {
constructor(
private injector: Injector,
@Optional() @SkipSelf() private _parent: CommandService,
) {}
async handleCommand<T>(command: string, data: T): Promise<T> {
const actions = this.getActions(command);
for (const action of actions) {
const handler = this.getActionHandler(action);
if (!handler) {
console.error(
'CommandService.handleCommand',
'Action Handler does not exist',
{ action },
);
throw new Error('Action Handler does not exist');
}
data = await handler.handler(data, this);
}
return data;
}
getActions(command: string) {
return command?.split('|') || [];
}
getActionHandler(action: string): ActionHandler | undefined {
const featureActionHandlers: ActionHandler[] = this.injector.get(
FEATURE_ACTION_HANDLERS,
[],
);
const rootActionHandlers: ActionHandler[] = this.injector.get(
ROOT_ACTION_HANDLERS,
[],
);
let handler = [...featureActionHandlers, ...rootActionHandlers].find(
(handler) => handler.action === action,
);
if (this._parent && !handler) {
handler = this._parent.getActionHandler(action);
}
return handler;
}
}

View File

@@ -72,12 +72,82 @@ import { ApplicationService } from '@core/application';
import { CustomerDTO } from '@generated/swagger/crm-api';
import { Config } from '@core/config';
import parseDuration from 'parse-duration';
import { CheckoutMetadataService } from '@isa/checkout/data-access';
import {
CheckoutMetadataService,
ShoppingCart,
} from '@isa/checkout/data-access';
import {
ShoppingCartEvent,
ShoppingCartEvents,
} from '@isa/checkout/data-access';
/**
* Domain service for managing the complete checkout flow including shopping cart operations,
* checkout creation, buyer/payer management, payment processing, and order completion.
*
* This service orchestrates interactions between:
* - NgRx Store for state management
* - Multiple Swagger API clients (checkout, OMS, shopping cart, payment, buyer, payer, branch, kulturpass)
* - Shopping cart event system for cross-component synchronization
* - Availability service for real-time product availability checks
*
* @remarks
* **Process ID Pattern**: All methods require a `processId` (typically `Date.now()`) to isolate
* checkout sessions. Multiple concurrent checkout processes can run independently.
*
* **Observable-First Design**: Most methods return Observables for reactive composition. Consumers
* should use RxJS operators for transformation and error handling.
*
* **Auto-Creation**: Shopping carts auto-create if missing. The service uses `filter()` operators
* to trigger lazy initialization and prevent race conditions.
*
* **Event Sourcing**: Publishes shopping cart events (Created, ItemAdded, ItemUpdated, ItemRemoved)
* for synchronization across components. Subscribes to events from `ShoppingCartService` to maintain
* consistency.
*
* **OLA Management**: Tracks Order Level Agreement (OLA) expiration timestamps per item and order type.
* Validates availability freshness before checkout completion.
*
* @example
* ```typescript
* // Basic shopping cart flow
* const processId = Date.now();
*
* // Add items to cart
* this.checkoutService.addItemToShoppingCart({
* processId,
* items: [{ productId: 123, quantity: 2 }]
* }).subscribe();
*
* // Get cart (auto-creates if missing)
* this.checkoutService.getShoppingCart({ processId })
* .subscribe(cart => console.log(cart));
*
* // Complete checkout (orchestrates all steps)
* this.checkoutService.completeCheckout({ processId })
* .subscribe(orders => console.log('Orders created:', orders));
* ```
*
* @see DomainCheckoutSelectors For state selection patterns
* @see DomainCheckoutActions For available actions
* @see ShoppingCartEvents For event system integration
*/
@Injectable()
export class DomainCheckoutService {
/** Metadata service for shopping cart persistence */
#checkoutMetadataService = inject(CheckoutMetadataService);
/** Event bus for shopping cart synchronization across components */
#shoppingCartEvents = inject(ShoppingCartEvents);
/**
* Gets the OLA (Order Level Agreement) expiration duration in milliseconds.
*
* OLA expiration defines how long availability data remains valid before requiring refresh.
* Default is 5 minutes if not configured.
*
* @returns Duration in milliseconds
*/
get olaExpiration() {
const exp = this._config.get('@domain/checkout.olaExpiration') ?? '5m';
return parseDuration(exp);
@@ -96,9 +166,56 @@ export class DomainCheckoutService {
private _payerService: StoreCheckoutPayerService,
private _branchService: StoreCheckoutBranchService,
private _kulturpassService: KulturPassService,
) {}
) {
// Subscribe to shopping cart events from ShoppingCartService
this.#shoppingCartEvents.events$
.pipe(
// Only process events from ShoppingCartService to avoid circular updates
filter((payload) => payload.source === 'ShoppingCartService'),
)
.subscribe((payload) => {
// Update the store with the shopping cart from the event
this.store.dispatch(
DomainCheckoutActions.setShoppingCartByShoppingCartId({
shoppingCartId: payload.shoppingCart.id!,
shoppingCart: payload.shoppingCart as any,
}),
);
});
}
//#region shoppingcart
/**
* Retrieves the shopping cart for a given process ID. Auto-creates the cart if it doesn't exist.
*
* @remarks
* **Auto-Creation**: If no cart exists for the process ID, triggers `createShoppingCart()` automatically.
* The Observable filters out null/undefined and waits for cart creation to complete.
*
* **Latest Data**: Setting `latest: true` forces a refresh from the API instead of using cached state.
* This is useful before critical operations like checkout completion.
*
* **Memoization**: Uses `@memorize()` decorator to cache results by parameters, reducing duplicate calls.
*
* @param params - Parameters object
* @param params.processId - Unique process identifier (typically `Date.now()`)
* @param params.latest - If true, fetches fresh data from API; if false/undefined, uses store state
*
* @returns Observable of the shopping cart DTO. Never emits null/undefined.
*
* @example
* ```typescript
* // Get cart from store (creates if missing)
* this.checkoutService.getShoppingCart({ processId: 123 })
* .pipe(first())
* .subscribe(cart => console.log('Items:', cart.items));
*
* // Force refresh from API
* this.checkoutService.getShoppingCart({ processId: 123, latest: true })
* .pipe(first())
* .subscribe(cart => console.log('Fresh cart:', cart));
* ```
*/
@memorize()
getShoppingCart({
processId,
@@ -127,7 +244,6 @@ export class DomainCheckoutService {
.pipe(
map((response) => response.result),
tap((shoppingCart) => {
this.updateProcessCount(processId, shoppingCart);
this.store.dispatch(
DomainCheckoutActions.setShoppingCart({
processId,
@@ -144,6 +260,24 @@ export class DomainCheckoutService {
);
}
/**
* Reloads the shopping cart from the API and updates the store with fresh data.
*
* This is an async method that fetches the latest cart state from the backend
* and dispatches an action to update the NgRx store. Unlike `getShoppingCart({ latest: true })`,
* this method doesn't return the cart Observable - it's fire-and-forget.
*
* @param params - Parameters object
* @param params.processId - Process identifier
*
* @returns Promise that resolves when reload completes (or immediately if no cart exists)
*
* @example
* ```typescript
* await this.checkoutService.reloadShoppingCart({ processId: 123 });
* console.log('Cart reloaded');
* ```
*/
async reloadShoppingCart({ processId }: { processId: number }) {
const shoppingCart = await firstValueFrom(
this.store.select(DomainCheckoutSelectors.selectShoppingCartByProcessId, {
@@ -159,7 +293,6 @@ export class DomainCheckoutService {
}),
);
this.updateProcessCount(processId, cart.result);
this.store.dispatch(
DomainCheckoutActions.setShoppingCart({
processId,
@@ -168,6 +301,29 @@ export class DomainCheckoutService {
);
}
/**
* Creates a new shopping cart and associates it with the given process ID.
*
* @remarks
* **State Updates**:
* - Saves shopping cart ID to metadata service for persistence
* - Publishes `ShoppingCartEvent.Created` event for component synchronization
* - Dispatches `setShoppingCart` action to update NgRx store
*
* **Auto-Invocation**: Usually called automatically by `getShoppingCart()` when no cart exists.
* Rarely needs to be called directly.
*
* @param params - Parameters object
* @param params.processId - Process identifier to associate with the new cart
*
* @returns Observable of the newly created shopping cart DTO
*
* @example
* ```typescript
* this.checkoutService.createShoppingCart({ processId: Date.now() })
* .subscribe(cart => console.log('Cart created:', cart.id));
* ```
*/
createShoppingCart({
processId,
}: {
@@ -182,6 +338,11 @@ export class DomainCheckoutService {
processId,
shoppingCart.id,
);
this.#shoppingCartEvents.pub(
ShoppingCartEvent.Created,
shoppingCart as ShoppingCart,
'DomainCheckoutService',
);
this.store.dispatch(
DomainCheckoutActions.setShoppingCart({
processId,
@@ -192,6 +353,41 @@ export class DomainCheckoutService {
);
}
/**
* Adds one or more items to the shopping cart.
*
* @remarks
* **Process Flow**:
* 1. Retrieves existing shopping cart (creates if missing)
* 2. Calls API to add items
* 3. Publishes `ShoppingCartEvent.ItemAdded` event
* 4. Updates NgRx store with modified cart
*
* **Validation**: Ensure items are validated via `canAddItem()` or `canAddItems()` before calling
* this method to avoid API errors.
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.items - Array of items to add (product, quantity, availability, destination, etc.)
*
* @returns Observable of the updated shopping cart with new items
*
* @example
* ```typescript
* this.checkoutService.addItemToShoppingCart({
* processId: 123,
* items: [{
* product: { ean: '1234567890', catalogProductNumber: 456 },
* quantity: 2,
* availability: availabilityDto,
* destination: destinationDto
* }]
* }).subscribe(cart => console.log('Items:', cart.items.length));
* ```
*
* @see canAddItem For single item validation
* @see canAddItems For bulk item validation
*/
addItemToShoppingCart({
processId,
items,
@@ -210,7 +406,11 @@ export class DomainCheckoutService {
.pipe(
map((response) => response.result),
tap((shoppingCart) => {
this.updateProcessCount(processId, shoppingCart);
this.#shoppingCartEvents.pub(
ShoppingCartEvent.ItemAdded,
shoppingCart as ShoppingCart,
'DomainCheckoutService',
);
this.store.dispatch(
DomainCheckoutActions.setShoppingCart({
processId,
@@ -270,6 +470,37 @@ export class DomainCheckoutService {
);
}
/**
* Validates if a single item can be added to the shopping cart.
*
* Checks business rules, customer features, and cart compatibility before adding items.
* Use this before calling `addItemToShoppingCart()` to prevent API errors.
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.availability - OLA availability data for the item
* @param params.orderType - Order type (e.g., 'Abholung', 'Versand', 'Download', 'Rücklage')
*
* @returns Observable of `true` if item can be added, or error message string if not allowed
*
* @example
* ```typescript
* this.checkoutService.canAddItem({
* processId: 123,
* availability: olaAvailability,
* orderType: 'Versand'
* }).subscribe(result => {
* if (result === true) {
* // Proceed with adding item
* this.checkoutService.addItemToShoppingCart(...);
* } else {
* console.error('Cannot add item:', result);
* }
* });
* ```
*
* @see canAddItems For bulk validation
*/
canAddItem({
processId,
availability,
@@ -315,6 +546,38 @@ export class DomainCheckoutService {
.pipe(map((response) => response?.result));
}
/**
* Validates if multiple items can be added to the shopping cart in bulk.
*
* More efficient than calling `canAddItem()` multiple times. Returns validation
* results for each item in the payload.
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.payload - Array of item payloads to validate
* @param params.orderType - Order type for all items
*
* @returns Observable array of validation results (one per item). Each result contains
* `ok` flag and optional error messages.
*
* @example
* ```typescript
* this.checkoutService.canAddItems({
* processId: 123,
* payload: [
* { availabilities: [avail1], productId: 111, quantity: 2 },
* { availabilities: [avail2], productId: 222, quantity: 1 }
* ],
* orderType: 'Versand'
* }).subscribe(results => {
* results.forEach((result, index) => {
* console.log(`Item ${index}:`, result.ok ? 'Valid' : result.message);
* });
* });
* ```
*
* @see canAddItem For single item validation
*/
canAddItems({
processId,
payload,
@@ -386,6 +649,50 @@ export class DomainCheckoutService {
);
}
/**
* Updates an existing item in the shopping cart (quantity, availability, special comment, etc.).
*
* @remarks
* **Special Behavior**:
* - Setting `quantity: 0` removes the item and publishes `ItemRemoved` event instead of `ItemUpdated`
* - Always fetches latest cart state (`latest: true`) to avoid stale data conflicts
* - If availability is updated, adds timestamp to history for OLA validation
*
* **Event Publishing**:
* - Publishes `ShoppingCartEvent.ItemRemoved` if quantity is 0
* - Publishes `ShoppingCartEvent.ItemUpdated` for all other changes
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.shoppingCartItemId - ID of the cart item to update
* @param params.update - Fields to update (quantity, availability, specialComment, etc.)
*
* @returns Observable of the updated shopping cart
*
* @example
* ```typescript
* // Update quantity
* this.checkoutService.updateItemInShoppingCart({
* processId: 123,
* shoppingCartItemId: 456,
* update: { quantity: 5 }
* }).subscribe();
*
* // Remove item (quantity = 0)
* this.checkoutService.updateItemInShoppingCart({
* processId: 123,
* shoppingCartItemId: 456,
* update: { quantity: 0 }
* }).subscribe();
*
* // Update availability
* this.checkoutService.updateItemInShoppingCart({
* processId: 123,
* shoppingCartItemId: 456,
* update: { availability: newAvailabilityDto }
* }).subscribe();
* ```
*/
updateItemInShoppingCart({
processId,
shoppingCartItemId,
@@ -407,6 +714,17 @@ export class DomainCheckoutService {
.pipe(
map((response) => response.result),
tap((shoppingCart) => {
// Check if item was removed (quantity === 0)
const eventType =
update.quantity === 0
? ShoppingCartEvent.ItemRemoved
: ShoppingCartEvent.ItemUpdated;
this.#shoppingCartEvents.pub(
eventType,
shoppingCart as ShoppingCart,
'DomainCheckoutService',
);
this.store.dispatch(
DomainCheckoutActions.setShoppingCart({
processId,
@@ -425,8 +743,6 @@ export class DomainCheckoutService {
),
);
}
this.updateProcessCount(processId, shoppingCart);
}),
),
),
@@ -437,6 +753,34 @@ export class DomainCheckoutService {
//#region Checkout
/**
* Retrieves the checkout entity for a given process. Auto-creates if missing.
*
* @remarks
* **Auto-Creation**: Similar to `getShoppingCart()`, automatically triggers `createCheckout()`
* if no checkout exists for the process ID.
*
* **Refresh**: Setting `refresh: true` forces recreation of the checkout entity from the API.
*
* **Purpose**: The checkout entity aggregates buyer, payer, payment, destinations, and
* notification channels. It's required before order completion.
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.refresh - If true, recreates checkout from API; if false/undefined, uses store state
*
* @returns Observable of the checkout DTO. Never emits null/undefined.
*
* @example
* ```typescript
* this.checkoutService.getCheckout({ processId: 123 })
* .pipe(first())
* .subscribe(checkout => {
* console.log('Buyer:', checkout.buyer);
* console.log('Payment:', checkout.payment);
* });
* ```
*/
getCheckout({
processId,
refresh,
@@ -777,6 +1121,40 @@ export class DomainCheckoutService {
);
}
/**
* Refreshes the availability data for a single shopping cart item.
*
* Fetches fresh availability from the appropriate service based on order type
* (Abholung, Rücklage, Download, Versand, DIG-Versand, B2B-Versand) and updates
* the cart item.
*
* @remarks
* **Order Type Handling**:
* - **Abholung** (Pickup): Requires branch for availability check
* - **Rücklage** (TakeAway): Requires branch for availability check
* - **Download**: No additional parameters needed
* - **Versand** (Delivery): Standard delivery availability
* - **DIG-Versand** (Digital Delivery): Digital goods delivery
* - **B2B-Versand** (B2B Delivery): Business customer delivery
*
* **Updates**: Automatically calls `updateItemInShoppingCart()` with the new availability
* after fetching.
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.shoppingCartItemId - ID of the cart item to refresh
*
* @returns Promise of the refreshed availability DTO, or undefined if item not found
*
* @example
* ```typescript
* const availability = await this.checkoutService.refreshAvailability({
* processId: 123,
* shoppingCartItemId: 456
* });
* console.log('Updated availability:', availability);
* ```
*/
async refreshAvailability({
processId,
shoppingCartItemId,
@@ -804,7 +1182,7 @@ export class DomainCheckoutService {
let availability: AvailabilityDTO;
switch (item.features.orderType) {
case 'Abholung':
case 'Abholung': {
const abholung = await this.availabilityService
.getPickUpAvailability({
item: itemData,
@@ -814,7 +1192,8 @@ export class DomainCheckoutService {
.toPromise();
availability = abholung[0];
break;
case 'Rücklage':
}
case 'Rücklage': {
const ruecklage = await this.availabilityService
.getTakeAwayAvailability({
item: itemData,
@@ -824,7 +1203,8 @@ export class DomainCheckoutService {
.toPromise();
availability = ruecklage;
break;
case 'Download':
}
case 'Download': {
const download = await this.availabilityService
.getDownloadAvailability({
item: itemData,
@@ -833,8 +1213,8 @@ export class DomainCheckoutService {
availability = download;
break;
case 'Versand':
}
case 'Versand': {
const versand = await this.availabilityService
.getDeliveryAvailability({
item: itemData,
@@ -844,8 +1224,8 @@ export class DomainCheckoutService {
availability = versand;
break;
case 'DIG-Versand':
}
case 'DIG-Versand': {
const digVersand = await this.availabilityService
.getDigDeliveryAvailability({
item: itemData,
@@ -855,8 +1235,8 @@ export class DomainCheckoutService {
availability = digVersand;
break;
case 'B2B-Versand':
}
case 'B2B-Versand': {
const b2bVersand = await this.availabilityService
.getB2bDeliveryAvailability({
item: itemData,
@@ -866,11 +1246,17 @@ export class DomainCheckoutService {
availability = b2bVersand;
break;
}
}
await this.updateItemInShoppingCart({
processId,
update: { availability },
update: {
availability: {
...availability,
price: item?.availability?.price ?? availability?.price,
}, // #5488 After Refreshing Availabilities in Cart make sure to keep the original selected price from purchasing options modal
},
shoppingCartItemId: item.id,
}).toPromise();
@@ -878,9 +1264,41 @@ export class DomainCheckoutService {
}
/**
* Check if the availability of all items is valid
* @param param0 Process Id
* @returns true if the availability of all items is valid
* Validates if all shopping cart items have fresh availability data (OLA not expired).
*
* OLA (Order Level Agreement) defines how long availability data remains valid.
* This method polls the store at regular intervals and checks if the oldest
* availability timestamp is still within the expiration window.
*
* @remarks
* **Polling**: Uses `rxjsInterval()` to continuously check OLA status. The Observable emits
* `true` while all items are valid, `false` when any item expires.
*
* **Timestamp Tracking**: Tracks timestamps per `${itemId}_${orderType}` combination.
* Shipping types (Versand, DIG-Versand, B2B-Versand) fall back to generic 'Versand' timestamp.
*
* **Default Interval**: Polls every `olaExpiration / 10` milliseconds (default: 30 seconds for 5-minute expiration).
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.interval - Custom polling interval in milliseconds (optional)
*
* @returns Observable that emits `true` when OLA is valid, `false` when expired.
* Emits only on changes (`distinctUntilChanged()`).
*
* @example
* ```typescript
* this.checkoutService.validateOlaStatus({ processId: 123 })
* .subscribe(isValid => {
* if (!isValid) {
* console.warn('Availability data expired! Refresh required.');
* // Trigger availability refresh
* }
* });
* ```
*
* @see olaExpiration For expiration duration configuration
* @see checkoutIsValid For combined OLA + availability validation
*/
validateOlaStatus({
processId,
@@ -967,6 +1385,39 @@ export class DomainCheckoutService {
);
}
/**
* Validates if the checkout is ready for order completion.
*
* Combines OLA status validation with availability validation. Both must be true
* for checkout to proceed.
*
* @remarks
* **Validation Checks**:
* - OLA Status: All item availabilities are within expiration window
* - Availabilities: All items are marked as available (not out of stock)
*
* **Polling**: Uses fast polling (250ms) for OLA status to catch expiration quickly.
*
* @param params - Parameters object
* @param params.processId - Process identifier
*
* @returns Observable that emits `true` when checkout is valid, `false` otherwise.
* Emits on every change in either validation.
*
* @example
* ```typescript
* this.checkoutService.checkoutIsValid({ processId: 123 })
* .subscribe(isValid => {
* this.checkoutButton.disabled = !isValid;
* if (!isValid) {
* this.showWarning('Checkout unavailable: Availability expired');
* }
* });
* ```
*
* @see validateOlaStatus For OLA-only validation
* @see validateAvailabilities For availability-only validation
*/
checkoutIsValid({ processId }: { processId: number }): Observable<boolean> {
const olaStatus$ = this.validateOlaStatus({ processId, interval: 250 });
@@ -977,6 +1428,73 @@ export class DomainCheckoutService {
);
}
/**
* Orchestrates the complete checkout process from cart validation to order creation.
*
* This is the most complex method in the service, executing a 12-step sequence that
* validates data, updates entities, and creates orders. Each step must complete before
* the next begins.
*
* @remarks
* **Execution Sequence** (sequential, not parallel):
* 1. **Update Destination**: Sets shipping addresses on delivery destinations
* 2. **Refresh Shopping Cart**: Gets latest cart state from API
* 3. **Set Special Comments**: Applies agent comments to all cart items
* 4. **Refresh Checkout**: Recreates checkout entity from current state
* 5. **Check Availabilities**: Validates download items are available
* 6. **Update Availabilities**: Refreshes DIG-Versand and B2B-Versand prices
* 7. **Set Buyer**: Submits buyer information to checkout
* 8. **Set Notification Channels**: Configures email/SMS preferences
* 9. **Set Payer**: Submits payer information (if needed for order type)
* 10. **Set Payment Type**: Configures payment method (Rechnung/Bar)
* 11. **Set Destination**: Updates destinations with shipping addresses
* 12. **Complete Order**: Submits to OMS for order creation
*
* **Payment Type Logic**:
* - Download/Versand/DIG-Versand/B2B-Versand → Payment type 128 (Rechnung/Invoice)
* - Pickup/TakeAway only → Payment type 4 (Bar/Cash)
*
* **Payer Requirement**:
* - Required for B2B customers or Download/Delivery order types
* - Skipped for in-store pickup/takeaway only
*
* **Error Handling**:
* - HTTP 409 (Conflict): Order already exists - dispatches existing orders to store
* - Other errors propagate to consumer for handling
* - Failed availability checks throw error preventing order creation
*
* **Side Effects**:
* - Logs each step to console (for debugging)
* - Updates NgRx store at multiple points
* - Dispatches final orders to store on success
*
* @param params - Parameters object
* @param params.processId - Process identifier
*
* @returns Observable array of created orders (DisplayOrderDTO[])
*
* @throws Observable error if availability validation fails or API returns non-409 error
*
* @example
* ```typescript
* this.checkoutService.completeCheckout({ processId: 123 })
* .subscribe({
* next: (orders) => {
* console.log('Orders created:', orders);
* this.router.navigate(['/order-confirmation']);
* },
* error: (error) => {
* if (error.status === 409) {
* console.log('Order already exists');
* } else {
* console.error('Checkout failed:', error);
* }
* }
* });
* ```
*
* @see completeKulturpassOrder For Kulturpass-specific checkout flow
*/
completeCheckout({
processId,
}: {
@@ -1330,11 +1848,45 @@ export class DomainCheckoutService {
//#region Common
// Fix für Ticket #4619 Versand Artikel im Warenkob -> keine Änderung bei Kundendaten erfassen
// Auskommentiert, da dieser Aufruf oftmals mit gleichen Parametern aufgerufen wird (ohne ausgewählten Kunden nur ein leeres Objekt bei customerFeatures)
// memorize macht keinen deepCompare von Objekten und denkt hier, dass immer der gleiche Return Wert zurückkommt, allerdings ist das hier oft nicht der Fall
// und der Decorator memorized dann fälschlicherweise
// @memorize()
/**
* Validates if a customer can be set on the shopping cart based on cart contents and customer features.
*
* @remarks
* **Memoization Disabled**: The `@memorize()` decorator was intentionally disabled for this method
* due to shallow comparison issues. The decorator couldn't detect when `customerFeatures` object
* changed, causing stale cached results. See Ticket #4619.
*
* **Response Fields**:
* - `ok`: True if customer can be set without issues
* - `filter`: Customer search filters (e.g., `{ customertype: 'webshop;guest' }`)
* - `message`: Error message if validation fails
* - `create`: Options for creating new customer types (store, guest, webshop, b2b)
*
* **Use Cases**:
* - Determine which customer types are compatible with cart contents
* - Pre-filter customer search results
* - Enable/disable customer type creation buttons
*
* @param params - Parameters object
* @param params.processId - Process identifier
* @param params.customerFeatures - Customer feature flags (optional: webshop, guest, b2b, staff, etc.)
*
* @returns Observable with validation result containing ok, filter, message, and create options
*
* @example
* ```typescript
* this.checkoutService.canSetCustomer({
* processId: 123,
* customerFeatures: { webshop: 'true', guest: 'false' }
* }).subscribe(result => {
* if (result.ok) {
* console.log('Customer types allowed:', result.create.options.values);
* } else {
* console.error('Cannot set customer:', result.message);
* }
* });
* ```
*/
canSetCustomer({
processId,
customerFeatures,
@@ -1429,7 +1981,7 @@ export class DomainCheckoutService {
): Observable<{ [key: string]: boolean }> {
return this.canSetCustomer({ processId, customerFeatures: undefined }).pipe(
map((res) => {
let setableTypes: { [key: string]: boolean } = {
const setableTypes: { [key: string]: boolean } = {
store: false,
guest: false,
webshop: false,
@@ -1469,6 +2021,32 @@ export class DomainCheckoutService {
);
}
/**
* Retrieves all active, online branches that support shipping.
*
* @remarks
* **Filtering**: Returns only branches matching ALL criteria:
* - `status === 1` (Active)
* - `branchType === 1` (Standard branch type)
* - `isOnline === true` (Available online)
* - `isShippingEnabled === true` (Supports shipping)
*
* **Memoization**: Uses `@memorize()` decorator to cache results. Subsequent calls
* return cached data without API round-trip.
*
* **Pagination**: Fetches up to 999 branches (effectively all branches).
*
* @returns Observable array of filtered branch DTOs
*
* @example
* ```typescript
* this.checkoutService.getBranches()
* .subscribe(branches => {
* console.log('Available branches:', branches.length);
* this.branchDropdown.options = branches;
* });
* ```
*/
@memorize()
getBranches(): Observable<BranchDTO[]> {
return this._branchService
@@ -1549,6 +2127,21 @@ export class DomainCheckoutService {
);
}
/**
* Removes all checkout data for a process ID from the store.
*
* Cleans up shopping cart, checkout entity, buyer, payer, and all associated data.
* Call this when a checkout session is complete or cancelled.
*
* @param params - Parameters object
* @param params.processId - Process identifier to remove
*
* @example
* ```typescript
* // After successful order or when user cancels
* this.checkoutService.removeProcess({ processId: 123 });
* ```
*/
removeProcess({ processId }: { processId: number }) {
this.store.dispatch(
DomainCheckoutActions.removeCheckoutWithProcessId({ processId }),
@@ -1624,13 +2217,4 @@ export class DomainCheckoutService {
});
}
//#endregion
//#region Common
async updateProcessCount(processId: number, shoppingCart: ShoppingCartDTO) {
this.applicationService.patchProcessData(processId, {
count: shoppingCart.items?.length ?? 0,
});
}
//#endregion
}

View File

@@ -19,6 +19,11 @@ export const setShoppingCart = createAction(
props<{ processId: number; shoppingCart: ShoppingCartDTO }>(),
);
export const setShoppingCartByShoppingCartId = createAction(
`${prefix} Set Shopping Cart By Shopping Cart Id`,
props<{ shoppingCartId: number; shoppingCart: ShoppingCartDTO }>(),
);
export const setCheckout = createAction(
`${prefix} Set Checkout`,
props<{ processId: number; checkout: CheckoutDTO }>(),

View File

@@ -1,207 +1,311 @@
import { createReducer, on } from '@ngrx/store';
import { initialCheckoutState, storeCheckoutAdapter } from './domain-checkout.state';
import * as DomainCheckoutActions from './domain-checkout.actions';
import { Dictionary } from '@ngrx/entity';
import { CheckoutEntity } from './defs/checkout.entity';
import { isNullOrUndefined } from '@utils/common';
const _domainCheckoutReducer = createReducer(
initialCheckoutState,
on(DomainCheckoutActions.setShoppingCart, (s, { processId, shoppingCart }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
const addedShoppingCartItems =
shoppingCart?.items
?.filter((item) => !entity.shoppingCart?.items?.find((i) => i.id === item.id))
?.map((item) => item.data) ?? [];
entity.shoppingCart = shoppingCart;
entity.itemAvailabilityTimestamp = entity.itemAvailabilityTimestamp ? { ...entity.itemAvailabilityTimestamp } : {};
const now = Date.now();
for (let shoppingCartItem of addedShoppingCartItems) {
if (shoppingCartItem.features?.orderType) {
entity.itemAvailabilityTimestamp[`${shoppingCartItem.id}_${shoppingCartItem.features.orderType}`] = now;
}
}
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setCheckout, (s, { processId, checkout }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.checkout = checkout;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setBuyerCommunicationDetails, (s, { processId, email, mobile }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
const communicationDetails = { ...entity.buyer.communicationDetails };
communicationDetails.email = email || communicationDetails.email;
communicationDetails.mobile = mobile || communicationDetails.mobile;
entity.buyer = {
...entity.buyer,
communicationDetails,
};
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setNotificationChannels, (s, { processId, notificationChannels }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
return storeCheckoutAdapter.setOne({ ...entity, notificationChannels }, s);
}),
on(DomainCheckoutActions.setCheckoutDestination, (s, { processId, destination }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.checkout = {
...entity.checkout,
destinations: entity.checkout.destinations.map((dest) => {
if (dest.id === destination.id) {
return { ...dest, ...destination };
}
return { ...dest };
}),
};
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setShippingAddress, (s, { processId, shippingAddress }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.shippingAddress = shippingAddress;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setBuyer, (s, { processId, buyer }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.buyer = buyer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setPayer, (s, { processId, payer }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.payer = payer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setSpecialComment, (s, { processId, agentComment }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.specialComment = agentComment;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.removeCheckoutWithProcessId, (s, { processId }) => {
return storeCheckoutAdapter.removeOne(processId, s);
}),
on(DomainCheckoutActions.setOrders, (s, { orders }) => ({ ...s, orders: [...s.orders, ...orders] })),
on(DomainCheckoutActions.updateOrderItem, (s, { item }) => {
const orders = [...s.orders];
const orderToUpdate = orders?.find((order) => order.items?.find((i) => i.id === item?.id));
const orderToUpdateIndex = orders?.indexOf(orderToUpdate);
const orderItemToUpdate = orderToUpdate?.items?.find((i) => i.id === item?.id);
const orderItemToUpdateIndex = orderToUpdate?.items?.indexOf(orderItemToUpdate);
const items = [...orderToUpdate?.items];
items[orderItemToUpdateIndex] = item;
orders[orderToUpdateIndex] = {
...orderToUpdate,
items: [...items],
};
return { ...s, orders: [...orders] };
}),
on(DomainCheckoutActions.removeAllOrders, (s) => ({
...s,
orders: [],
})),
on(DomainCheckoutActions.setOlaError, (s, { processId, olaErrorIds }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.olaErrorIds = olaErrorIds;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setCustomer, (s, { processId, customer }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
entity.customer = customer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(
DomainCheckoutActions.addShoppingCartItemAvailabilityToHistory,
(s, { processId, shoppingCartItemId, availability }) => {
const entity = getOrCreateCheckoutEntity({ processId, entities: s.entities });
const itemAvailabilityTimestamp = entity?.itemAvailabilityTimestamp
? { ...entity?.itemAvailabilityTimestamp }
: {};
const item = entity?.shoppingCart?.items?.find((i) => i.id === shoppingCartItemId)?.data;
if (!item?.features?.orderType) return s;
itemAvailabilityTimestamp[`${item.id}_${item?.features?.orderType}`] = Date.now();
entity.itemAvailabilityTimestamp = itemAvailabilityTimestamp;
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(
DomainCheckoutActions.addShoppingCartItemAvailabilityToHistoryByShoppingCartId,
(s, { shoppingCartId, shoppingCartItemId, availability }) => {
const entity = getCheckoutEntityByShoppingCartId({ shoppingCartId, entities: s.entities });
const itemAvailabilityTimestamp = entity?.itemAvailabilityTimestamp
? { ...entity?.itemAvailabilityTimestamp }
: {};
const item = entity?.shoppingCart?.items?.find((i) => i.id === shoppingCartItemId)?.data;
if (!item?.features?.orderType) return s;
itemAvailabilityTimestamp[`${item.id}_${item?.features?.orderType}`] = Date.now();
entity.itemAvailabilityTimestamp = itemAvailabilityTimestamp;
return storeCheckoutAdapter.setOne(entity, s);
},
),
);
export function domainCheckoutReducer(state, action) {
return _domainCheckoutReducer(state, action);
}
function getOrCreateCheckoutEntity({
entities,
processId,
}: {
entities: Dictionary<CheckoutEntity>;
processId: number;
}): CheckoutEntity {
let entity = entities[processId];
if (isNullOrUndefined(entity)) {
return {
processId,
checkout: undefined,
shoppingCart: undefined,
shippingAddress: undefined,
orders: [],
payer: undefined,
buyer: undefined,
specialComment: '',
notificationChannels: 0,
olaErrorIds: [],
customer: undefined,
// availabilityHistory: [],
itemAvailabilityTimestamp: {},
};
}
return { ...entity };
}
function getCheckoutEntityByShoppingCartId({
entities,
shoppingCartId,
}: {
entities: Dictionary<CheckoutEntity>;
shoppingCartId: number;
}): CheckoutEntity {
return Object.values(entities).find((entity) => entity.shoppingCart?.id === shoppingCartId);
}
import { createReducer, on } from '@ngrx/store';
import {
initialCheckoutState,
storeCheckoutAdapter,
} from './domain-checkout.state';
import * as DomainCheckoutActions from './domain-checkout.actions';
import { Dictionary } from '@ngrx/entity';
import { CheckoutEntity } from './defs/checkout.entity';
import { isNullOrUndefined } from '@utils/common';
const _domainCheckoutReducer = createReducer(
initialCheckoutState,
on(
DomainCheckoutActions.setShoppingCart,
(s, { processId, shoppingCart }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
const addedShoppingCartItems =
shoppingCart?.items
?.filter(
(item) =>
!entity.shoppingCart?.items?.find((i) => i.id === item.id),
)
?.map((item) => item.data) ?? [];
entity.shoppingCart = shoppingCart;
entity.itemAvailabilityTimestamp = entity.itemAvailabilityTimestamp
? { ...entity.itemAvailabilityTimestamp }
: {};
const now = Date.now();
for (const shoppingCartItem of addedShoppingCartItems) {
if (shoppingCartItem.features?.orderType) {
entity.itemAvailabilityTimestamp[
`${shoppingCartItem.id}_${shoppingCartItem.features.orderType}`
] = now;
}
}
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(
DomainCheckoutActions.setShoppingCartByShoppingCartId,
(s, { shoppingCartId, shoppingCart }) => {
let entity = getCheckoutEntityByShoppingCartId({
shoppingCartId,
entities: s.entities,
});
if (!entity) {
// No entity found for this shoppingCartId, cannot update
return s;
}
entity = { ...entity, shoppingCart };
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(DomainCheckoutActions.setCheckout, (s, { processId, checkout }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.checkout = checkout;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(
DomainCheckoutActions.setBuyerCommunicationDetails,
(s, { processId, email, mobile }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
const communicationDetails = { ...entity.buyer.communicationDetails };
communicationDetails.email = email || communicationDetails.email;
communicationDetails.mobile = mobile || communicationDetails.mobile;
entity.buyer = {
...entity.buyer,
communicationDetails,
};
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(
DomainCheckoutActions.setNotificationChannels,
(s, { processId, notificationChannels }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
return storeCheckoutAdapter.setOne(
{ ...entity, notificationChannels },
s,
);
},
),
on(
DomainCheckoutActions.setCheckoutDestination,
(s, { processId, destination }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.checkout = {
...entity.checkout,
destinations: entity.checkout.destinations.map((dest) => {
if (dest.id === destination.id) {
return { ...dest, ...destination };
}
return { ...dest };
}),
};
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(
DomainCheckoutActions.setShippingAddress,
(s, { processId, shippingAddress }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.shippingAddress = shippingAddress;
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(DomainCheckoutActions.setBuyer, (s, { processId, buyer }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.buyer = buyer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setPayer, (s, { processId, payer }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.payer = payer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(
DomainCheckoutActions.setSpecialComment,
(s, { processId, agentComment }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.specialComment = agentComment;
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(DomainCheckoutActions.removeCheckoutWithProcessId, (s, { processId }) => {
return storeCheckoutAdapter.removeOne(processId, s);
}),
on(DomainCheckoutActions.setOrders, (s, { orders }) => ({
...s,
orders: [...s.orders, ...orders],
})),
on(DomainCheckoutActions.updateOrderItem, (s, { item }) => {
const orders = [...s.orders];
const orderToUpdate = orders?.find((order) =>
order.items?.find((i) => i.id === item?.id),
);
const orderToUpdateIndex = orders?.indexOf(orderToUpdate);
const orderItemToUpdate = orderToUpdate?.items?.find(
(i) => i.id === item?.id,
);
const orderItemToUpdateIndex =
orderToUpdate?.items?.indexOf(orderItemToUpdate);
const items = [...(orderToUpdate?.items ?? [])];
items[orderItemToUpdateIndex] = item;
orders[orderToUpdateIndex] = {
...orderToUpdate,
items: [...items],
};
return { ...s, orders: [...orders] };
}),
on(DomainCheckoutActions.removeAllOrders, (s) => ({
...s,
orders: [],
})),
on(DomainCheckoutActions.setOlaError, (s, { processId, olaErrorIds }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.olaErrorIds = olaErrorIds;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(DomainCheckoutActions.setCustomer, (s, { processId, customer }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
entity.customer = customer;
return storeCheckoutAdapter.setOne(entity, s);
}),
on(
DomainCheckoutActions.addShoppingCartItemAvailabilityToHistory,
(s, { processId, shoppingCartItemId, availability }) => {
const entity = getOrCreateCheckoutEntity({
processId,
entities: s.entities,
});
const itemAvailabilityTimestamp = entity?.itemAvailabilityTimestamp
? { ...entity?.itemAvailabilityTimestamp }
: {};
const item = entity?.shoppingCart?.items?.find(
(i) => i.id === shoppingCartItemId,
)?.data;
if (!item?.features?.orderType) return s;
itemAvailabilityTimestamp[`${item.id}_${item?.features?.orderType}`] =
Date.now();
entity.itemAvailabilityTimestamp = itemAvailabilityTimestamp;
return storeCheckoutAdapter.setOne(entity, s);
},
),
on(
DomainCheckoutActions.addShoppingCartItemAvailabilityToHistoryByShoppingCartId,
(s, { shoppingCartId, shoppingCartItemId, availability }) => {
const entity = getCheckoutEntityByShoppingCartId({
shoppingCartId,
entities: s.entities,
});
const itemAvailabilityTimestamp = entity?.itemAvailabilityTimestamp
? { ...entity?.itemAvailabilityTimestamp }
: {};
const item = entity?.shoppingCart?.items?.find(
(i) => i.id === shoppingCartItemId,
)?.data;
if (!item?.features?.orderType) return s;
itemAvailabilityTimestamp[`${item.id}_${item?.features?.orderType}`] =
Date.now();
entity.itemAvailabilityTimestamp = itemAvailabilityTimestamp;
return storeCheckoutAdapter.setOne(entity, s);
},
),
);
export function domainCheckoutReducer(state, action) {
return _domainCheckoutReducer(state, action);
}
function getOrCreateCheckoutEntity({
entities,
processId,
}: {
entities: Dictionary<CheckoutEntity>;
processId: number;
}): CheckoutEntity {
const entity = entities[processId];
if (isNullOrUndefined(entity)) {
return {
processId,
checkout: undefined,
shoppingCart: undefined,
shippingAddress: undefined,
orders: [],
payer: undefined,
buyer: undefined,
specialComment: '',
notificationChannels: 0,
olaErrorIds: [],
customer: undefined,
// availabilityHistory: [],
itemAvailabilityTimestamp: {},
};
}
return { ...entity };
}
function getCheckoutEntityByShoppingCartId({
entities,
shoppingCartId,
}: {
entities: Dictionary<CheckoutEntity>;
shoppingCartId: number;
}): CheckoutEntity {
return Object.values(entities).find(
(entity) => entity.shoppingCart?.id === shoppingCartId,
);
}

View File

File diff suppressed because it is too large Load Diff

View File

@@ -20,9 +20,15 @@ export class PrintShippingNoteActionHandler extends ActionHandler<OrderItemsCont
async printShippingNoteHelper(printer: string, receipts: ReceiptDTO[]) {
try {
for (const group of groupBy(receipts, (receipt) => receipt?.buyer?.buyerNumber)) {
for (const group of groupBy(
receipts,
(receipt) => receipt?.buyer?.buyerNumber,
)) {
await this.domainPrinterService
.printShippingNote({ printer, receipts: group?.items?.map((r) => r?.id) })
.printShippingNote({
printer,
receipts: group?.items?.map((r) => r?.id),
})
.toPromise();
}
return {
@@ -38,7 +44,9 @@ export class PrintShippingNoteActionHandler extends ActionHandler<OrderItemsCont
}
async handler(data: OrderItemsContext): Promise<OrderItemsContext> {
const printerList = await this.domainPrinterService.getAvailableLabelPrinters().toPromise();
const printerList = await this.domainPrinterService
.getAvailableLabelPrinters()
.toPromise();
const receipts = data?.receipts?.filter((r) => r?.receiptType & 1);
let printer: Printer;
@@ -53,7 +61,8 @@ export class PrintShippingNoteActionHandler extends ActionHandler<OrderItemsCont
data: {
printImmediately: !this._environmentSerivce.matchTablet(),
printerType: 'Label',
print: async (printer) => await this.printShippingNoteHelper(printer, receipts),
print: async (printer) =>
await this.printShippingNoteHelper(printer, receipts),
} as PrintModalData,
})
.afterClosed$.toPromise();

View File

@@ -0,0 +1,313 @@
# Purchase Options Modal
The Purchase Options Modal allows users to select how they want to receive their items (delivery, pickup, in-store, download) during the checkout process.
## Overview
This modal handles the complete purchase option selection flow including:
- Fetching availability for each purchase option
- Validating if items can be added to the shopping cart
- Managing item quantities and prices
- Supporting reward redemption flows
## Features
### Core Functionality
- **Multiple Purchase Options**: Delivery, B2B Delivery, Digital Delivery, Pickup, In-Store, Download
- **Availability Checking**: Real-time availability checks for each option
- **Branch Selection**: Pick branches for pickup and in-store options
- **Price Management**: Handle pricing, VAT, and manual price adjustments
- **Reward Redemption**: Support for redeeming loyalty points
### Advanced Features
- **Disabled Purchase Options**: Prevent specific options from being available (skips API calls)
- **Hide Disabled Options**: Toggle visibility of disabled options (show grayed out or hide completely)
- **Pre-selection**: Pre-select a specific purchase option on open
- **Single Option Mode**: Show only one specific purchase option
## Usage
### Basic Usage
```typescript
import { PurchaseOptionsModalService } from '@modal/purchase-options';
constructor(private purchaseOptionsModal: PurchaseOptionsModalService) {}
async openModal() {
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add', // or 'update'
items: [/* array of items */],
});
const result = await firstValueFrom(modalRef.afterClosed$);
}
```
### Disabling Purchase Options
Prevent specific options from being available. The modal will **not make API calls** for disabled options.
```typescript
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add',
items: [item1, item2],
disabledPurchaseOptions: ['b2b-delivery'], // Disable B2B delivery
});
```
### Hide vs Show Disabled Options
Control whether disabled options are hidden or shown with a disabled visual state:
**Hide Disabled Options (default)**
```typescript
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add',
items: [item],
disabledPurchaseOptions: ['b2b-delivery'],
hideDisabledPurchaseOptions: true, // Default - option not visible
});
```
**Show Disabled Options (grayed out)**
```typescript
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add',
items: [item],
disabledPurchaseOptions: ['b2b-delivery'],
hideDisabledPurchaseOptions: false, // Show disabled with visual indicator
});
```
### Pre-selecting an Option
```typescript
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add',
items: [item],
preSelectOption: {
option: 'in-store',
showOptionOnly: false, // Optional: show only this option
},
});
```
### Reward Redemption Flow
```typescript
const modalRef = await this.purchaseOptionsModal.open({
tabId: 123,
shoppingCartId: 456,
type: 'add',
items: [rewardItem],
useRedemptionPoints: true,
preSelectOption: { option: 'in-store' },
disabledPurchaseOptions: ['b2b-delivery'], // Common for rewards
});
```
## API Reference
### PurchaseOptionsModalData
```typescript
interface PurchaseOptionsModalData {
/** Tab ID for context */
tabId: number;
/** Shopping cart ID to add/update items */
shoppingCartId: number;
/** Action type: 'add' = new items, 'update' = existing items */
type: 'add' | 'update';
/** Enable redemption points mode */
useRedemptionPoints?: boolean;
/** Items to show in the modal */
items: Array<ItemDTO | ShoppingCartItemDTO>;
/** Pre-configured pickup branch */
pickupBranch?: BranchDTO;
/** Pre-configured in-store branch */
inStoreBranch?: BranchDTO;
/** Pre-select a specific purchase option */
preSelectOption?: {
option: PurchaseOption;
showOptionOnly?: boolean;
};
/** Purchase options to disable (no API calls) */
disabledPurchaseOptions?: PurchaseOption[];
/** Hide disabled options (true) or show as grayed out (false). Default: true */
hideDisabledPurchaseOptions?: boolean;
}
```
### PurchaseOption Type
```typescript
type PurchaseOption =
| 'delivery' // Standard delivery
| 'dig-delivery' // Digital delivery
| 'b2b-delivery' // B2B delivery
| 'pickup' // Pickup at branch
| 'in-store' // Reserve in store
| 'download' // Digital download
| 'catalog'; // Catalog availability
```
## Architecture
### Component Structure
```
purchase-options/
├── purchase-options-modal.component.ts # Main modal component
├── purchase-options-modal.service.ts # Service to open modal
├── purchase-options-modal.data.ts # Data interfaces
├── store/
│ ├── purchase-options.store.ts # NgRx ComponentStore
│ ├── purchase-options.service.ts # Business logic service
│ ├── purchase-options.state.ts # State interface
│ ├── purchase-options.types.ts # Type definitions
│ └── purchase-options.selectors.ts # State selectors
├── purchase-options-tile/
│ ├── base-purchase-option.directive.ts # Base directive for tiles
│ ├── delivery-purchase-options-tile.component.ts
│ ├── pickup-purchase-options-tile.component.ts
│ ├── in-store-purchase-options-tile.component.ts
│ └── download-purchase-options-tile.component.ts
└── purchase-options-list-item/ # Item list components
```
### State Management
The modal uses NgRx ComponentStore for state management:
- **Availability Loading**: Parallel API calls for each enabled option
- **Can Add Validation**: Check if items can be added to cart
- **Item Selection**: Track selected items for batch operations
- **Branch Management**: Handle branch selection for pickup/in-store
### Disabled Options Flow
1. **Configuration**: `disabledPurchaseOptions` array passed to modal
2. **State**: Stored in store via `initialize()` method
3. **Availability Loading**: `isOptionDisabled()` check skips API calls
4. **UI Rendering**:
- If `hideDisabledPurchaseOptions: true` → not rendered
- If `hideDisabledPurchaseOptions: false` → rendered with `.disabled` class
5. **Click Prevention**: Disabled tiles prevent click action
## Common Use Cases
### 1. Regular Checkout
```typescript
// Show all options
await modalService.open({
tabId: processId,
shoppingCartId: cartId,
type: 'add',
items: catalogItems,
});
```
### 2. Reward Redemption
```typescript
// Pre-select in-store, disable B2B
await modalService.open({
tabId: processId,
shoppingCartId: rewardCartId,
type: 'add',
items: rewardItems,
useRedemptionPoints: true,
preSelectOption: { option: 'in-store' },
disabledPurchaseOptions: ['b2b-delivery'],
});
```
### 3. Update Existing Item
```typescript
// Allow user to change delivery option
await modalService.open({
tabId: processId,
shoppingCartId: cartId,
type: 'update',
items: [existingCartItem],
});
```
### 4. Gift Cards (In-Store Only)
```typescript
// Show only in-store and delivery
await modalService.open({
tabId: processId,
shoppingCartId: cartId,
type: 'add',
items: [giftCardItem],
disabledPurchaseOptions: ['pickup', 'b2b-delivery'],
});
```
## Testing
### Running Tests
```bash
# Run all tests for the app
npx nx test isa-app --skip-nx-cache
```
### Testing Disabled Options
When testing the disabled options feature:
1. Verify no API calls are made for disabled options
2. Check UI rendering based on `hideDisabledPurchaseOptions` flag
3. Ensure click events are prevented on disabled tiles
4. Validate backward compatibility (defaults work correctly)
## Migration Notes
### From `hidePurchaseOptions` to `disabledPurchaseOptions`
The field was renamed for clarity:
- **Old**: `hidePurchaseOptions` (ambiguous - hides from UI)
- **New**: `disabledPurchaseOptions` (clear - disabled functionality, may or may not be hidden)
This is a **breaking change** if you were using `hidePurchaseOptions`. Update all usages:
```typescript
// Before
hidePurchaseOptions: ['b2b-delivery']
// After
disabledPurchaseOptions: ['b2b-delivery']
```
## Troubleshooting
### Problem: Disabled option still making API calls
**Solution**: Ensure the option is in the `disabledPurchaseOptions` array and spelled correctly.
### Problem: Disabled option not showing even with `hideDisabledPurchaseOptions: false`
**Solution**: Check that `showOption()` logic and availability checks are working correctly.
### Problem: All options disabled
**Solution**: Don't disable all options. At least one option must be available for users to proceed.
## Related Documentation
- [Checkout Data Access](../../../libs/checkout/data-access/README.md)
- [Shopping Cart Flow](../../page/checkout/README.md)
- [Reward System](../../../libs/checkout/feature/reward-catalog/README.md)

View File

@@ -5,7 +5,7 @@ import {
VATValueDTO,
} from '@generated/swagger/checkout-api';
import { PurchaseOption } from './store';
import { OrderType } from '@isa/checkout/data-access';
import { OrderTypeFeature } from '@isa/checkout/data-access';
export const PURCHASE_OPTIONS: PurchaseOption[] = [
'in-store',
@@ -23,7 +23,7 @@ export const DELIVERY_PURCHASE_OPTIONS: PurchaseOption[] = [
];
export const PURCHASE_OPTION_TO_ORDER_TYPE: {
[purchaseOption: string]: OrderType;
[purchaseOption: string]: OrderTypeFeature;
} = {
'in-store': 'Rücklage',
'pickup': 'Abholung',

View File

@@ -242,6 +242,14 @@
}
}
@if (showNoDownloadAvailability$ | async) {
<span
class="inline-block font-bold text-[#BE8100] mt-[14px] max-w-[19rem]"
>
Derzeit nicht verfügbar
</span>
}
@if (showMaxAvailableQuantity$ | async) {
<span class="font-bold text-[#BE8100] mt-[14px]">
{{ (availability$ | async)?.inStock }} Exemplare sofort lieferbar

View File

@@ -36,6 +36,7 @@ import { GIFT_CARD_MAX_PRICE, PRICE_PATTERN } from '../constants';
import {
Item,
PurchaseOptionsStore,
isDownload,
isItemDTO,
isShoppingCartItemDTO,
} from '../store';
@@ -222,13 +223,23 @@ export class PurchaseOptionsListItemComponent
}),
);
fetchingAvailabilities$ = this.item$
.pipe(
switchMap((item) =>
this._store.getFetchingAvailabilitiesForItem$(item.id),
),
)
.pipe(map((fetchingAvailabilities) => fetchingAvailabilities.length > 0));
fetchingAvailabilitiesArray$ = this.item$.pipe(
switchMap((item) => this._store.getFetchingAvailabilitiesForItem$(item.id)),
);
fetchingAvailabilities$ = this.fetchingAvailabilitiesArray$.pipe(
map((fetchingAvailabilities) => fetchingAvailabilities.length > 0),
);
fetchingInStoreAvailability$ = this.fetchingAvailabilitiesArray$.pipe(
map((fetchingAvailabilities) =>
fetchingAvailabilities.some((fa) => fa.purchaseOption === 'in-store'),
),
);
isFetchingInStore = toSignal(this.fetchingInStoreAvailability$, {
initialValue: false,
});
showNotAvailable$ = combineLatest([
this.availabilities$,
@@ -247,6 +258,35 @@ export class PurchaseOptionsListItemComponent
}),
);
isDownload$ = this.item$.pipe(map((item) => isDownload(item)));
isDownloadItem = toSignal(this.isDownload$, { initialValue: false });
showNoDownloadAvailability$ = combineLatest([
this.isDownload$,
this.availabilities$,
this.fetchingAvailabilities$,
]).pipe(
map(([isDownloadItem, availabilities, fetchingAvailabilities]) => {
// Only check for download items
if (!isDownloadItem) {
return false;
}
// Don't show error while loading
if (fetchingAvailabilities) {
return false;
}
// Check if download availability exists
const hasDownloadAvailability = availabilities.some(
(a) => a.purchaseOption === 'download',
);
return !hasDownloadAvailability;
}),
);
// Ticket #4813 Artikeldetailseite // EVT-Datum bei der Kaufoption Rücklage anzeigen
get isEVT() {
// Einstieg über Kaufoptionen - Hier wird die Katalogavailability verwendet die am ItemDTO hängt
@@ -279,10 +319,16 @@ export class PurchaseOptionsListItemComponent
});
showLowStockMessage = computed(() => {
const availability = this.availability();
const inStock = availability?.inStock ?? 0;
return (
this.useRedemptionPoints() &&
this.isReservePurchaseOption() &&
(!this.availability() || this.availability().inStock < 2)
!this.isDownloadItem() &&
!this.isFetchingInStore() &&
inStock > 0 &&
inStock < 2
);
});

View File

@@ -20,6 +20,7 @@ import {
PickupPurchaseOptionTileComponent,
} from './purchase-options-tile';
import {
isDownload,
isGiftCard,
Item,
PurchaseOption,
@@ -102,19 +103,16 @@ export class PurchaseOptionsModalComponent implements OnInit, OnDestroy {
purchasingOptions$ = this.store.getPurchaseOptionsInAvailabilities$;
isDownloadOnly$ = this.purchasingOptions$.pipe(
map(
(purchasingOptions) =>
purchasingOptions.length === 1 && purchasingOptions[0] === 'download',
),
isDownloadOnly$ = this.store.items$.pipe(
map((items) => items.length > 0 && items.every((item) => isDownload(item))),
);
isGiftCardOnly$ = this.store.items$.pipe(
map((items) => items.every((item) => isGiftCard(item, this.store.type))),
);
hasDownload$ = this.purchasingOptions$.pipe(
map((purchasingOptions) => purchasingOptions.includes('download')),
hasDownload$ = this.store.items$.pipe(
map((items) => items.some((item) => isDownload(item))),
);
canContinue$ = this.store.canContinue$;
@@ -154,7 +152,32 @@ export class PurchaseOptionsModalComponent implements OnInit, OnDestroy {
itemTrackBy: TrackByFunction<Item> = (_, item) => item.id;
/**
* Determines if a purchase option should be shown in the UI.
*
* Evaluation order:
* 1. If option is disabled AND hideDisabledPurchaseOptions is true -> hide (return false)
* 2. If preSelectOption.showOptionOnly is true -> show only that option
* 3. Otherwise -> show the option
*
* @param option - The purchase option to check
* @returns true if the option should be displayed, false otherwise
*
* @example
* ```typescript
* // In template
* @if (showOption('delivery')) {
* <app-delivery-purchase-options-tile></app-delivery-purchase-options-tile>
* }
* ```
*/
showOption(option: PurchaseOption): boolean {
const disabledOptions = this._uiModalRef.data?.disabledPurchaseOptions ?? [];
const hideDisabled = this._uiModalRef.data?.hideDisabledPurchaseOptions ?? true;
if (disabledOptions.includes(option) && hideDisabled) {
return false;
}
return this._uiModalRef.data?.preSelectOption?.showOptionOnly
? this._uiModalRef.data?.preSelectOption?.option === option
: true;

View File

@@ -6,25 +6,125 @@ import {
import { Customer } from '@isa/crm/data-access';
import { ActionType, PurchaseOption } from './store';
/**
* Data interface for opening the Purchase Options Modal.
*
* @example
* ```typescript
* // Basic usage
* const modalRef = await purchaseOptionsModalService.open({
* tabId: 123,
* shoppingCartId: 456,
* type: 'add',
* items: [item1, item2],
* });
*
* // With disabled options
* const modalRef = await purchaseOptionsModalService.open({
* tabId: 123,
* shoppingCartId: 456,
* type: 'add',
* items: [rewardItem],
* disabledPurchaseOptions: ['b2b-delivery'],
* hideDisabledPurchaseOptions: true, // Hide completely (default)
* });
* ```
*/
export interface PurchaseOptionsModalData {
/** Tab ID for maintaining context across the application */
tabId: number;
/** Shopping cart ID where items will be added or updated */
shoppingCartId: number;
/**
* Action type determining modal behavior:
* - 'add': Adding new items to cart
* - 'update': Updating existing cart items
*/
type: ActionType;
/**
* Enable redemption points mode for reward items.
* When true, prices are set to 0 and loyalty points are applied.
*/
useRedemptionPoints?: boolean;
/** Items to display in the modal for purchase option selection */
items: Array<ItemDTO | ShoppingCartItemDTO>;
/** Pre-configured branch for pickup option */
pickupBranch?: BranchDTO;
/** Pre-configured branch for in-store option */
inStoreBranch?: BranchDTO;
/**
* Pre-select a specific purchase option on modal open.
* Set showOptionOnly to true to display only that option.
*/
preSelectOption?: { option: PurchaseOption; showOptionOnly?: boolean };
/**
* Purchase options to disable. Disabled options:
* - Will not have availability API calls made
* - Will either be hidden or shown as disabled based on hideDisabledPurchaseOptions
*
* @example ['b2b-delivery', 'download']
*/
disabledPurchaseOptions?: PurchaseOption[];
/**
* Controls visibility of disabled purchase options.
* - true (default): Disabled options are completely hidden from the UI
* - false: Disabled options are shown with a disabled visual state (grayed out, not clickable)
*
* @default true
*/
hideDisabledPurchaseOptions?: boolean;
}
/**
* Internal context interface used within the modal component.
* Extends PurchaseOptionsModalData with additional runtime data like selected customer.
*
* @internal
*/
export interface PurchaseOptionsModalContext {
/** Shopping cart ID where items will be added or updated */
shoppingCartId: number;
/**
* Action type determining modal behavior:
* - 'add': Adding new items to cart
* - 'update': Updating existing cart items
*/
type: ActionType;
/** Enable redemption points mode for reward items */
useRedemptionPoints: boolean;
/** Items to display in the modal for purchase option selection */
items: Array<ItemDTO | ShoppingCartItemDTO>;
/** Customer selected in the current tab (resolved at runtime) */
selectedCustomer?: Customer;
/** Default branch resolved from user settings or tab context */
selectedBranch?: BranchDTO;
/** Pre-configured branch for pickup option */
pickupBranch?: BranchDTO;
/** Pre-configured branch for in-store option */
inStoreBranch?: BranchDTO;
/** Pre-select a specific purchase option on modal open */
preSelectOption?: { option: PurchaseOption; showOptionOnly?: boolean };
/** Purchase options to disable (no API calls, conditional UI rendering) */
disabledPurchaseOptions?: PurchaseOption[];
/** Controls visibility of disabled purchase options (default: true = hidden) */
hideDisabledPurchaseOptions?: boolean;
}

View File

@@ -1,4 +1,4 @@
import { Injectable, inject } from '@angular/core';
import { Injectable, inject, untracked } from '@angular/core';
import { UiModalRef, UiModalService } from '@ui/modal';
import { PurchaseOptionsModalComponent } from './purchase-options-modal.component';
import {
@@ -10,13 +10,63 @@ import {
Customer,
CrmTabMetadataService,
} from '@isa/crm/data-access';
import { TabService } from '@isa/core/tabs';
import { BranchDTO } from '@generated/swagger/checkout-api';
import { CheckoutMetadataService } from '@isa/checkout/data-access';
/**
* Service for opening and managing the Purchase Options Modal.
*
* The Purchase Options Modal allows users to select how they want to receive items
* (delivery, pickup, in-store, download) and manages availability checking, pricing,
* and shopping cart operations.
*
* @example
* ```typescript
* // Basic usage
* const modalRef = await this.purchaseOptionsModalService.open({
* tabId: 123,
* shoppingCartId: 456,
* type: 'add',
* items: [item1, item2],
* });
*
* // Await modal close
* const result = await firstValueFrom(modalRef.afterClosed$);
* ```
*/
@Injectable({ providedIn: 'root' })
export class PurchaseOptionsModalService {
#uiModal = inject(UiModalService);
#tabService = inject(TabService);
#crmTabMetadataService = inject(CrmTabMetadataService);
#checkoutMetadataService = inject(CheckoutMetadataService);
#customerFacade = inject(CustomerFacade);
/**
* Opens the Purchase Options Modal.
*
* @param data - Configuration data for the modal
* @returns Promise resolving to a modal reference
*
* @example
* ```typescript
* // Add new items with disabled B2B delivery
* const modalRef = await this.purchaseOptionsModalService.open({
* tabId: processId,
* shoppingCartId: cartId,
* type: 'add',
* items: [item1, item2],
* disabledPurchaseOptions: ['b2b-delivery'],
* });
*
* // Wait for modal to close
* const action = await firstValueFrom(modalRef.afterClosed$);
* if (action === 'continue') {
* // Proceed to next step
* }
* ```
*/
async open(
data: PurchaseOptionsModalData,
): Promise<UiModalRef<string, PurchaseOptionsModalData>> {
@@ -26,7 +76,10 @@ export class PurchaseOptionsModalService {
};
context.selectedCustomer = await this.#getSelectedCustomer(data);
context.selectedBranch = this.#getSelectedBranch(
data.tabId,
data.useRedemptionPoints,
);
return this.#uiModal.open<string, PurchaseOptionsModalContext>({
content: PurchaseOptionsModalComponent,
data: context,
@@ -46,4 +99,32 @@ export class PurchaseOptionsModalService {
return this.#customerFacade.fetchCustomer({ customerId });
}
#getSelectedBranch(
tabId: number,
useRedemptionPoints: boolean,
): BranchDTO | undefined {
const tab = untracked(() =>
this.#tabService.entities().find((t) => t.id === tabId),
);
if (!tab) {
return undefined;
}
if (useRedemptionPoints) {
return this.#checkoutMetadataService.getSelectedBranch(tabId);
}
const legacyProcessData = tab?.metadata?.process_data;
if (
typeof legacyProcessData === 'object' &&
'selectedBranch' in legacyProcessData
) {
return legacyProcessData.selectedBranch as BranchDTO;
}
return undefined;
}
}

View File

@@ -2,6 +2,27 @@ import { ChangeDetectorRef, Directive, HostBinding, HostListener } from '@angula
import { asapScheduler } from 'rxjs';
import { PurchaseOption, PurchaseOptionsStore } from '../store';
/**
* Base directive for purchase option tile components.
*
* Provides common functionality for all purchase option tiles:
* - Visual selected state binding
* - Visual disabled state binding
* - Click handling with disabled check
* - Auto-selection of available items
*
* @example
* ```typescript
* export class DeliveryPurchaseOptionTileComponent extends BasePurchaseOptionDirective {
* constructor(
* protected store: PurchaseOptionsStore,
* protected cdr: ChangeDetectorRef,
* ) {
* super('delivery');
* }
* }
* ```
*/
@Directive({
standalone: false,
})
@@ -9,15 +30,46 @@ export abstract class BasePurchaseOptionDirective {
protected abstract store: PurchaseOptionsStore;
protected abstract cdr: ChangeDetectorRef;
/**
* Binds the 'selected' CSS class to the host element.
* Applied when this purchase option is the currently selected one.
*/
@HostBinding('class.selected')
get selected() {
return this.store.purchaseOption === this.purchaseOption;
}
/**
* Binds the 'disabled' CSS class to the host element.
* Applied when this purchase option is in the disabledPurchaseOptions array.
* Disabled options:
* - Have no availability API calls made
* - Are shown with reduced opacity and not-allowed cursor
* - Prevent click interactions
*/
@HostBinding('class.disabled')
get disabled() {
return this.store.disabledPurchaseOptions.includes(this.purchaseOption);
}
constructor(protected purchaseOption: PurchaseOption) {}
/**
* Handles click events on the purchase option tile.
*
* Behavior:
* 1. If disabled, prevents any action
* 2. Sets this option as the selected purchase option
* 3. Resets selected items
* 4. Auto-selects all items that have availability and can be added for this option
*
* @listens click
*/
@HostListener('click')
setPurchaseOptions() {
if (this.disabled) {
return;
}
this.store.setPurchaseOption(this.purchaseOption);
this.store.resetSelectedItems();
asapScheduler.schedule(() => {

View File

@@ -10,6 +10,10 @@
@apply bg-[#D8DFE5] border-[#0556B4];
}
:host.disabled {
@apply opacity-50 cursor-not-allowed bg-gray-100;
}
.purchase-options-tile__heading {
@apply flex flex-row justify-center items-center;
}

View File

@@ -13,7 +13,7 @@ import {
ItemPayloadWithSourceId,
PurchaseOption,
} from './purchase-options.types';
import { OrderType } from '@isa/checkout/data-access';
import { OrderTypeFeature } from '@isa/checkout/data-access';
export function isItemDTO(item: any, type: ActionType): item is ItemDTO {
return type === 'add';
@@ -145,7 +145,7 @@ export function mapToOlaAvailability({
export function getOrderTypeForPurchaseOption(
purchaseOption: PurchaseOption,
): OrderType | undefined {
): OrderTypeFeature | undefined {
switch (purchaseOption) {
case 'delivery':
case 'dig-delivery':
@@ -163,7 +163,7 @@ export function getOrderTypeForPurchaseOption(
}
export function getPurchaseOptionForOrderType(
orderType: OrderType,
orderType: OrderTypeFeature,
): PurchaseOption | undefined {
switch (orderType) {
case 'Versand':

View File

@@ -17,7 +17,10 @@ import { memorize } from '@utils/common';
import { AuthService } from '@core/auth';
import { ApplicationService } from '@core/application';
import { DomainOmsService } from '@domain/oms';
import { OrderType, PurchaseOptionsFacade } from '@isa/checkout/data-access';
import {
OrderTypeFeature,
PurchaseOptionsFacade,
} from '@isa/checkout/data-access';
@Injectable({ providedIn: 'root' })
export class PurchaseOptionsService {
@@ -28,19 +31,12 @@ export class PurchaseOptionsService {
private _checkoutService: DomainCheckoutService,
private _omsService: DomainOmsService,
private _auth: AuthService,
private _app: ApplicationService,
) {}
getVats$() {
return this._omsService.getVATs();
}
getSelectedBranchForProcess(processId: number): Observable<Branch> {
return this._app
.getSelectedBranch$(processId)
.pipe(take(1), shareReplay(1));
}
getCustomerFeatures(processId: number): Observable<Record<string, string>> {
return this._checkoutService
.getCustomerFeatures({ processId })
@@ -122,7 +118,7 @@ export class PurchaseOptionsService {
fetchCanAdd(
shoppingCartId: number,
orderType: OrderType,
orderType: OrderTypeFeature,
payload: ItemPayload[],
customerFeatures: Record<string, string>,
): Promise<ItemsResult[]> {
@@ -185,10 +181,11 @@ export class PurchaseOptionsService {
items,
});
console.log('added item to cart', { shoppingCart });
this._checkoutService.updateProcessCount(
this._app.activatedProcessId,
shoppingCart,
);
// FIX BUILD ERRORS
// this._checkoutService.updateProcessCount(
// this._app.activatedProcessId,
// shoppingCart,
// );
return shoppingCart;
}
@@ -203,10 +200,11 @@ export class PurchaseOptionsService {
values: payload,
});
console.log('updated item in cart', { shoppingCart });
this._checkoutService.updateProcessCount(
this._app.activatedProcessId,
shoppingCart,
);
// FIX BUILD ERRORS
// this._checkoutService.updateProcessCount(
// this._app.activatedProcessId,
// shoppingCart,
// );
}
@memorize({ comparer: (_) => true })

View File

@@ -37,4 +37,6 @@ export interface PurchaseOptionsState {
fetchingAvailabilities: Array<FetchingAvailability>;
useRedemptionPoints: boolean;
disabledPurchaseOptions: PurchaseOption[];
}

View File

@@ -40,7 +40,12 @@ import { uniqueId } from 'lodash';
import { VATDTO } from '@generated/swagger/oms-api';
import { DomainCatalogService } from '@domain/catalog';
import { ItemDTO } from '@generated/swagger/cat-search-api';
import { Loyalty, OrderType, Promotion } from '@isa/checkout/data-access';
import {
Loyalty,
OrderTypeFeature,
Promotion,
} from '@isa/checkout/data-access';
import { ensureCurrencyDefaults } from '@isa/common/data-access';
@Injectable()
export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
@@ -152,6 +157,10 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
fetchingAvailabilities$ = this.select(Selectors.getFetchingAvailabilities);
get disabledPurchaseOptions() {
return this.get((s) => s.disabledPurchaseOptions);
}
get vats$() {
return this._service.getVats$();
}
@@ -181,6 +190,7 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
customerFeatures: {},
fetchingAvailabilities: [],
useRedemptionPoints: false,
disabledPurchaseOptions: [],
});
}
@@ -213,13 +223,14 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
inStoreBranch,
pickupBranch,
useRedemptionPoints: showRedemptionPoints,
disabledPurchaseOptions,
}: PurchaseOptionsModalContext) {
const defaultBranch = await this._service.fetchDefaultBranch().toPromise();
const customerFeatures =
selectedCustomer?.features.reduce(
(acc, feature) => {
acc[feature.key] = feature.value;
acc[feature.key] = feature.key;
return acc;
},
{} as Record<string, string>,
@@ -237,6 +248,7 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
pickupBranch: pickupBranch ?? selectedBranch,
inStoreBranch: inStoreBranch ?? selectedBranch,
customerFeatures,
disabledPurchaseOptions: disabledPurchaseOptions ?? [],
});
await this._loadAvailabilities();
@@ -246,6 +258,19 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
// #region Private funtions for loading and setting Branches and Availabilities
/**
* Checks if a purchase option is disabled.
* Disabled options will not have availability API calls made.
*
* @param option - The purchase option to check
* @returns true if the option is in the disabledPurchaseOptions array
*
* @private
*/
private isOptionDisabled(option: PurchaseOption): boolean {
return this.disabledPurchaseOptions.includes(option);
}
private async _loadAvailabilities() {
const items = this.items;
@@ -256,15 +281,27 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
items.forEach((item) => {
const itemData = mapToItemData(item, this.type);
if (isDownload(item)) {
promises.push(this._loadDownloadAvailability(itemData));
if (!this.isOptionDisabled('download')) {
promises.push(this._loadDownloadAvailability(itemData));
}
} else {
if (!isGiftCard(item, this.type)) {
promises.push(this._loadPickupAvailability(itemData));
promises.push(this._loadInStoreAvailability(itemData));
promises.push(this._loadDeliveryAvailability(itemData));
promises.push(this._loadDigDeliveryAvailability(itemData));
if (!this.isOptionDisabled('pickup')) {
promises.push(this._loadPickupAvailability(itemData));
}
if (!this.isOptionDisabled('in-store')) {
promises.push(this._loadInStoreAvailability(itemData));
}
if (!this.isOptionDisabled('delivery')) {
promises.push(this._loadDeliveryAvailability(itemData));
}
if (!this.isOptionDisabled('dig-delivery')) {
promises.push(this._loadDigDeliveryAvailability(itemData));
}
}
if (!this.isOptionDisabled('b2b-delivery')) {
promises.push(this._loadB2bDeliveryAvailability(itemData));
}
promises.push(this._loadB2bDeliveryAvailability(itemData));
}
});
@@ -282,18 +319,30 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
const itemData = mapToItemData(item, this.type);
if (purchaseOption === 'in-store' || purchaseOption === undefined) {
if (
(purchaseOption === 'in-store' || purchaseOption === undefined) &&
!this.isOptionDisabled('in-store')
) {
promises.push(this._loadInStoreAvailability(itemData));
}
if (purchaseOption === 'pickup' || purchaseOption === undefined) {
if (
(purchaseOption === 'pickup' || purchaseOption === undefined) &&
!this.isOptionDisabled('pickup')
) {
promises.push(this._loadPickupAvailability(itemData));
}
if (purchaseOption === 'delivery' || purchaseOption === undefined) {
promises.push(this._loadDeliveryAvailability(itemData));
promises.push(this._loadDigDeliveryAvailability(itemData));
promises.push(this._loadB2bDeliveryAvailability(itemData));
if (!this.isOptionDisabled('delivery')) {
promises.push(this._loadDeliveryAvailability(itemData));
}
if (!this.isOptionDisabled('dig-delivery')) {
promises.push(this._loadDigDeliveryAvailability(itemData));
}
if (!this.isOptionDisabled('b2b-delivery')) {
promises.push(this._loadB2bDeliveryAvailability(itemData));
}
}
await Promise.all(promises);
@@ -679,7 +728,7 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
try {
const res = await this._service.fetchCanAdd(
this.shoppingCartId,
key as OrderType,
key as OrderTypeFeature,
itemPayloads,
this.customerFeatures,
);
@@ -688,7 +737,9 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
this._addCanAddResult({
canAdd: canAdd.status === 0,
itemId: item.sourceId,
purchaseOption: getPurchaseOptionForOrderType(key as OrderType),
purchaseOption: getPurchaseOptionForOrderType(
key as OrderTypeFeature,
),
message: canAdd.message,
});
});
@@ -1018,7 +1069,7 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
throw new Error('Invalid item');
}
const price = this.getPriceForPurchaseOption(itemId, this.purchaseOption);
let price = this.getPriceForPurchaseOption(itemId, this.purchaseOption);
const availability = this.getAvailabilityWithPurchaseOption(
itemId,
purchaseOption,
@@ -1036,7 +1087,15 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
// Set loyalty points from item
loyalty = { value: redemptionPoints };
// Set price to 0
price.value.value = 0;
price = ensureCurrencyDefaults({
...price,
value: {
...price.value,
value: 0,
currency: 'EUR',
currencySymbol: '€',
},
});
}
let destination: EntityDTOContainerOfDestinationDTO;
@@ -1074,7 +1133,7 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
if (!isShoppingCartItemDTO(item, this.type)) {
throw new Error('Invalid item');
}
const price = this.getPriceForPurchaseOption(itemId, this.purchaseOption);
let price = this.getPriceForPurchaseOption(itemId, this.purchaseOption);
const availability = this.getAvailabilityWithPurchaseOption(
itemId,
purchaseOption,
@@ -1083,7 +1142,15 @@ export class PurchaseOptionsStore extends ComponentStore<PurchaseOptionsState> {
// If loyalty points is set we know it is a redemption item
// we need to make sure we don't update the price
if (this.useRedemptionPoints) {
price.value.value = 0;
price = ensureCurrencyDefaults({
...price,
value: {
...price.value,
value: 0,
currency: 'EUR',
currencySymbol: '€',
},
});
}
let destination: EntityDTOContainerOfDestinationDTO;

View File

@@ -7,8 +7,25 @@ import {
ShoppingCartItemDTO,
} from '@generated/swagger/checkout-api';
/**
* Action type for the purchase options modal.
* - 'add': Adding new items to the shopping cart
* - 'update': Updating existing items in the shopping cart
*/
export type ActionType = 'add' | 'update';
/**
* Available purchase options for item delivery/fulfillment.
*
* Each option represents a different way customers can receive their items:
* - `delivery`: Standard home/address delivery
* - `dig-delivery`: Digital delivery (special handling)
* - `b2b-delivery`: Business-to-business delivery
* - `pickup`: Pickup at a branch location
* - `in-store`: Reserve and collect in store
* - `download`: Digital download (e-books, digital content)
* - `catalog`: Catalog availability (reference only)
*/
export type PurchaseOption =
| 'delivery'
| 'dig-delivery'

View File

@@ -1,14 +1,19 @@
import { Routes } from '@angular/router';
import { AssortmentComponent } from './assortment.component';
import { PriceUpdateComponent } from './price-update/price-update.component';
export const routes: Routes = [
{
path: '',
component: AssortmentComponent,
children: [
{ path: 'price-update', component: PriceUpdateComponent },
{ path: '**', redirectTo: 'price-update' },
],
},
];
import { Routes } from '@angular/router';
import { AssortmentComponent } from './assortment.component';
import { PriceUpdateComponent } from './price-update/price-update.component';
export const routes: Routes = [
{
path: '',
component: AssortmentComponent,
title: 'Sortiment',
children: [
{
path: 'price-update',
component: PriceUpdateComponent,
title: 'Sortiment - Preisänderung',
},
{ path: '**', redirectTo: 'price-update' },
],
},
];

View File

@@ -1,4 +1,5 @@
import { Pipe, PipeTransform } from '@angular/core';
import { REIHE_PREFIX_PATTERN } from './reihe.constants';
@Pipe({
name: 'lineType',
@@ -7,8 +8,8 @@ import { Pipe, PipeTransform } from '@angular/core';
})
export class LineTypePipe implements PipeTransform {
transform(value: string, ...args: any[]): 'text' | 'reihe' {
const REIHE_REGEX = /^Reihe:\s*"(.+)\"$/g;
const reihe = REIHE_REGEX.exec(value)?.[1];
const REIHE_REGEX = new RegExp(`^${REIHE_PREFIX_PATTERN}:\\s*"(.+)"$`, 'g');
const reihe = REIHE_REGEX.exec(value)?.[2];
return reihe ? 'reihe' : 'text';
}
}

View File

@@ -1,9 +1,15 @@
import { ChangeDetectorRef, OnDestroy, Pipe, PipeTransform } from '@angular/core';
import {
ChangeDetectorRef,
OnDestroy,
Pipe,
PipeTransform,
} from '@angular/core';
import { ApplicationService } from '@core/application';
import { ProductCatalogNavigationService } from '@shared/services/navigation';
import { isEqual } from 'lodash';
import { Subscription, combineLatest, BehaviorSubject } from 'rxjs';
import { distinctUntilChanged } from 'rxjs/operators';
import { REIHE_PREFIX_PATTERN } from './reihe.constants';
@Pipe({
name: 'reiheRoute',
@@ -22,10 +28,13 @@ export class ReiheRoutePipe implements PipeTransform, OnDestroy {
private application: ApplicationService,
private cdr: ChangeDetectorRef,
) {
this.subscription = combineLatest([this.application.activatedProcessId$, this.value$])
this.subscription = combineLatest([
this.application.activatedProcessId$,
this.value$,
])
.pipe(distinctUntilChanged(isEqual))
.subscribe(([processId, value]) => {
const REIHE_REGEX = /[";]|Reihe:/g; // Entferne jedes Semikolon, Anführungszeichen und den String Reihe:
const REIHE_REGEX = new RegExp(`[";]|${REIHE_PREFIX_PATTERN}:`, 'g'); // Entferne jedes Semikolon, Anführungszeichen und den String Reihe:/Reihe/Set:/Set/Reihe:
const reihe = value?.replace(REIHE_REGEX, '')?.trim();
if (!reihe) {
@@ -33,9 +42,15 @@ export class ReiheRoutePipe implements PipeTransform, OnDestroy {
return;
}
const main_qs = reihe.split('/')[0];
// Entferne Zahlen am Ende, die mit Leerzeichen, Komma, Slash oder Semikolon getrennt sind
// Beispiele: "Harry Potter 1" -> "Harry Potter", "Harry Potter,1" -> "Harry Potter", "Harry Potter/2" -> "Harry Potter"
const main_qs = reihe
.split('/')[0]
.replace(/[\s,;]+\d+$/g, '')
.trim();
const path = this.navigation.getArticleSearchResultsPath(processId).path;
const path =
this.navigation.getArticleSearchResultsPath(processId).path;
this.result = {
path,

View File

@@ -0,0 +1,5 @@
/**
* Shared regex pattern for matching Reihe line prefixes.
* Matches: "Reihe:", "Reihe/Set:", or "Set/Reihe:"
*/
export const REIHE_PREFIX_PATTERN = '(Reihe|Reihe\\/Set|Set\\/Reihe)';

View File

@@ -55,8 +55,6 @@ import {
RewardSelectionPopUpService,
} from '@isa/checkout/shared/reward-selection-dialog';
import { injectConfirmationDialog, injectFeedbackDialog } from '@isa/ui/dialog';
@Component({
selector: 'page-article-details',
templateUrl: 'article-details.component.html',
@@ -210,7 +208,7 @@ export class ArticleDetailsComponent implements OnInit, OnDestroy {
).path;
}
showMore: boolean = false;
showMore = false;
@ViewChild('detailsContainer', { read: ElementRef, static: false })
detailsContainer: ElementRef;
@@ -610,7 +608,7 @@ export class ArticleDetailsComponent implements OnInit, OnDestroy {
async navigateToResultList() {
const processId = this.applicationService.activatedProcessId;
let crumbs = await this.breadcrumb
const crumbs = await this.breadcrumb
.getBreadcrumbsByKeyAndTags$(this.applicationService.activatedProcessId, [
'catalog',
'details',

View File

@@ -1,55 +1,47 @@
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { ArticleDetailsComponent } from './article-details.component';
import { ProductImageModule } from '@cdn/product-image';
import { UiIconModule } from '@ui/icon';
import { RouterModule } from '@angular/router';
import { UiStarsModule } from '@ui/stars';
import { UiSliderModule } from '@ui/slider';
import { ArticleRecommendationsComponent } from './recommendations/article-recommendations.component';
import { PipesModule } from '../shared/pipes/pipes.module';
import { UiTooltipModule } from '@ui/tooltip';
import { UiCommonModule } from '@ui/common';
import { OrderDeadlinePipeModule } from '@shared/pipes/order-deadline';
import { IconModule } from '@shared/components/icon';
import { ArticleDetailsTextComponent } from './article-details-text/article-details-text.component';
import { IconBadgeComponent } from 'apps/isa-app/src/shared/components/icon/badge/icon-badge.component';
import { MatomoModule } from 'ngx-matomo-client';
import {
SelectedRewardShoppingCartResource,
SelectedShoppingCartResource,
} from '@isa/checkout/data-access';
import { SelectedCustomerBonusCardsResource } from '@isa/crm/data-access';
import {
RewardSelectionService,
RewardSelectionPopUpService,
} from '@isa/checkout/shared/reward-selection-dialog';
@NgModule({
imports: [
CommonModule,
ProductImageModule,
UiIconModule,
RouterModule,
UiStarsModule,
UiSliderModule,
UiCommonModule,
UiTooltipModule,
IconModule,
PipesModule,
OrderDeadlinePipeModule,
ArticleDetailsTextComponent,
IconBadgeComponent,
MatomoModule,
],
exports: [ArticleDetailsComponent, ArticleRecommendationsComponent],
declarations: [ArticleDetailsComponent, ArticleRecommendationsComponent],
providers: [
SelectedShoppingCartResource,
SelectedRewardShoppingCartResource,
SelectedCustomerBonusCardsResource,
RewardSelectionService,
RewardSelectionPopUpService,
],
})
export class ArticleDetailsModule {}
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { ArticleDetailsComponent } from './article-details.component';
import { ProductImageModule } from '@cdn/product-image';
import { UiIconModule } from '@ui/icon';
import { RouterModule } from '@angular/router';
import { UiStarsModule } from '@ui/stars';
import { UiSliderModule } from '@ui/slider';
import { ArticleRecommendationsComponent } from './recommendations/article-recommendations.component';
import { PipesModule } from '../shared/pipes/pipes.module';
import { UiTooltipModule } from '@ui/tooltip';
import { UiCommonModule } from '@ui/common';
import { OrderDeadlinePipeModule } from '@shared/pipes/order-deadline';
import { IconModule } from '@shared/components/icon';
import { ArticleDetailsTextComponent } from './article-details-text/article-details-text.component';
import { IconBadgeComponent } from 'apps/isa-app/src/shared/components/icon/badge/icon-badge.component';
import { MatomoModule } from 'ngx-matomo-client';
import {
RewardSelectionService,
RewardSelectionPopUpService,
} from '@isa/checkout/shared/reward-selection-dialog';
@NgModule({
imports: [
CommonModule,
ProductImageModule,
UiIconModule,
RouterModule,
UiStarsModule,
UiSliderModule,
UiCommonModule,
UiTooltipModule,
IconModule,
PipesModule,
OrderDeadlinePipeModule,
ArticleDetailsTextComponent,
IconBadgeComponent,
MatomoModule,
],
exports: [ArticleDetailsComponent, ArticleRecommendationsComponent],
declarations: [ArticleDetailsComponent, ArticleRecommendationsComponent],
providers: [
RewardSelectionService,
RewardSelectionPopUpService,
],
})
export class ArticleDetailsModule {}

Some files were not shown because too many files have changed in this diff Show More