david
26e2ee59bd
- Implemented feedback state resolution for proforma list and update pages. - Created error view models for proforma and customer updates, including handling for various error types. - Added tests for error handling in proforma and customer list updates. - Introduced utility functions for building error view models and resolving feedback states. - Ensured translation support for error messages in Spanish. - Removed duplicate error alert components in customer module.
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# 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](./identity-and-companies.md)
|
|
- [Tenant context](./tenant-context.md)
|
|
- [Identity auth API](./identity-auth-api.md)
|
|
- [Tratamiento de errores HTTP en frontend](./http-error-handling-frontend.md)
|
|
- [Identity migration status](./identity-migration-status.md)
|
|
- [Identity roadmap](./identity-roadmap.md)
|
|
|
|
## Documentación complementaria
|
|
|
|
- [Identity backend architecture](./identity-backend-architecture.md)
|
|
|
|
`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
|
|
|
|
- `identity` gestiona autenticación, sesión, refresh y memberships.
|
|
- `companies` gestiona la ficha operativa de empresa.
|
|
- `GET /companies/available` es la vía vigente para companies accesibles.
|
|
- El contexto tenant se resuelve con `X-Company-Id` y `requireIdentityTenant(params)`.
|
|
- El frontend ERP ya usa el runtime nuevo de `identity`.
|