Best Practices in ARDOR

Writing maintainable frontend applications requires clear structural boundaries between state, transport, and dependency resolution. These best practices describe established patterns for registering container services, typing keys with module augmentation, authoring repositories, and handling token recovery.

Binding Keys and Registration

Register classes via stereotype discovery or by hand, manage singleton scopes, and wire provider slots

Module Augmentation

Extend key unions for useInjectable and useTranslate through TypeScript module augmentation on @venizia/ardor

Services and Repositories

Author domain services on BaseService and resource repositories on HttpRepository with options objects and @api()

No-Auth Paths and Token Recovery

Configure unauthenticated endpoints and implement one-refresh-one-retry recovery workflows for HTTP 401 statuses

Architecture Roadmap

1

Container Registration

Binding Keys and Registration

Choose between stereotype discovery and manual registration with singleton defaults

2

Type Safety

Module Augmentation

Augment the umbrella package to enforce strict type checking on injectable and translation keys

3

Domain Architecture

Services and Repositories

Build testable classes on BaseService and HttpRepository using options objects and error decorators

4

Authentication Security

No-Auth Paths and Token Recovery

Define unauthenticated paths and coordinate automatic token refresh across data providers and repositories