- Add utility functions for managing audit page state including parsing, serialization, and updates. - Introduce audit period resolution logic to handle various time frames. - Create API functions for finding and searching audit entries with appropriate DTOs and mappers. - Implement hooks for fetching audit entries and lists, integrating with the data source. - Add tests for utility functions, API calls, and mappers to ensure correctness. - Establish shared entities and DTOs for consistent data handling across the module. - Set up TypeScript configuration for the audit module. |
||
|---|---|---|
| .. | ||
| audit-system-design.md | ||
| http-error-handling-frontend.md | ||
| identity-and-companies.md | ||
| identity-auth-api.md | ||
| identity-backend-architecture.md | ||
| identity-migration-status.md | ||
| identity-roadmap.md | ||
| README.md | ||
| tenant-context.md | ||
ERP Architecture Docs
Índice de arquitectura vigente y documentos transicionales relacionados con autenticación, tenant context y migración a identity.
Documentación canónica vigente
- Identity and companies
- Tenant context
- Identity auth API
- Tratamiento de errores HTTP en frontend
- Identity migration status
- Identity roadmap
Documentación complementaria
identity-backend-architecture.md se mantiene como nota complementaria de diseño backend. Para contratos operativos concretos, prevalecen tenant-context.md, identity-auth-api.md y los README de módulo.
Resumen actual
identitygestiona autenticación, sesión, refresh y memberships.companiesgestiona la ficha operativa de empresa.GET /companies/availablees la vía vigente para companies accesibles.- El contexto tenant se resuelve con
X-Company-IdyrequireIdentityTenant(params). - El frontend ERP ya usa el runtime nuevo de
identity.