Rodax_Software/FactuGES_ERP
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
9c7dfc8645
FactuGES_ERP/apps/web/README.md

52 lines
1.7 KiB
Markdown
Raw Normal View History

Docs
2026-07-06 15:47:05 +00:00
# `apps/web`
Aplicación frontend principal del ERP.
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
## Documentación canónica
Docs
2026-07-06 15:47:05 +00:00
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
- Arquitectura, autenticación y selección de empresa: [`../../docs/frontend/frontend-architecture.md`](../../docs/frontend/frontend-architecture.md)
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
- Contexto tenant y reglas de `X-Company-Id`: [`../../docs/architecture/tenant-context.md`](../../docs/architecture/tenant-context.md)
feat: add error handling and feedback state management for customer and proforma updates - 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.
2026-08-06 11:03:48 +00:00
- Tratamiento de errores HTTP en frontend: [`../../docs/architecture/http-error-handling-frontend.md`](../../docs/architecture/http-error-handling-frontend.md)
Docs
2026-07-06 15:47:05 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
## Runtime actual de autenticación
Docs
2026-07-06 15:47:05 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
La app usa `@erp/identity/client` como runtime actual.
Docs
2026-07-06 15:47:05 +00:00
## Flujo actual
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
- La sesión y la empresa activa se resuelven según el flujo documentado en `docs/frontend/frontend-architecture.md`.
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
- Las rutas tenant-scoped deben respetar las reglas de `X-Company-Id` documentadas en `docs/architecture/tenant-context.md`.
Docs
2026-07-06 15:47:05 +00:00
## Headers
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
- No duplicar aquí la matriz de headers.
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
- Consultar `docs/frontend/frontend-architecture.md` para endpoints excluidos y `tenant-context.md` para reglas tenant-scoped.
Docs
2026-07-06 15:47:05 +00:00
## App company switcher
Componente:
```txt
apps/web/src/layout/app-company-switcher.tsx
```
Propósito:
- mostrar la empresa activa real en el layout autenticado
- permitir cambiar entre `availableCompanies` de la sesión actual
Reglas:
- usar el contexto de `identity`
- no manejar tokens
- no llamar directamente a `GET /companies/available`
- no usar `companySlug` para auth
- no modificar el access token
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
- respetar el flujo canónico documentado en `docs/frontend/frontend-architecture.md`
Docs
2026-07-06 15:47:05 +00:00
## Refresh automático
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources.
2026-08-05 11:18:03 +00:00
La app implementa refresh automático global sobre `401`.
Docs
2026-07-06 15:47:05 +00:00
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
La semántica completa de retry, exclusiones y limpieza de sesión se documenta en `docs/frontend/frontend-architecture.md`.
Reference in New Issue Copy Permalink