Rodax_Software/FactuGES_ERP
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
a4f82decc6
FactuGES_ERP/docs/architecture
History
david a4f82decc6 feat(companies): implement update current company use case and associated controllers 
- Add UpdateCurrentCompanyUseCase to handle company updates.
- Create update-current-company.controller.ts to manage update requests.
- Implement validation and mapping for update requests using Zod.
- Add tests for the update use case and controller to ensure functionality.
- Introduce error handling and feedback state management for company details settings.
- Create utility functions for error normalization and feedback state resolution.
- Implement tests for error handling and feedback state utilities.
- Ensure nullable fields are handled correctly in DTOs and forms.
2026-08-17 15:49:11 +02:00
..
http-error-handling-frontend.md feat: add error handling and feedback state management for customer and proforma updates 2026-08-06 13:03:48 +02:00
identity-and-companies.md feat(companies): implement update current company use case and associated controllers 2026-08-17 15:49:11 +02:00
identity-auth-api.md Docs 2026-07-06 17:47:05 +02:00
identity-backend-architecture.md Refactor documentation for ERP architecture and customer invoices 2026-08-05 13:18:03 +02:00
identity-migration-status.md feat(companies): implement update current company use case and associated controllers 2026-08-17 15:49:11 +02:00
identity-roadmap.md Doc 2026-07-06 14:04:47 +02:00
README.md feat: add error handling and feedback state management for customer and proforma updates 2026-08-06 13:03:48 +02:00
tenant-context.md feat(companies): implement update current company use case and associated controllers 2026-08-17 15:49:11 +02:00

README.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

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

  • 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.