david
cf07de4836
- Implemented `evaluateProformaCustomerChange` function to assess changes in customer details for proforma invoices. - Introduced types for customer change details, blockers, field differences, and fiscal targets. - Added utility functions for normalizing text and formatting recipient information. test: add unit tests for customer payment resolver - Created tests for `CustomerPaymentResolver` to validate payment term retrieval and handling of inactive terms. - Ensured proper behavior when clearing payment terms and handling non-existent terms. test: add unit tests for customer default payment term resolver - Developed tests for `CustomerDefaultPaymentTermResolver` to verify default payment term resolution logic. - Included scenarios for creating customers with and without explicit payment term IDs. feat: implement customer default payment term resolver - Created `CustomerDefaultPaymentTermResolver` to manage default payment term resolution during customer creation. - Integrated with company finder and payment resolver services. test: add unit tests for create customer use case - Implemented tests for `CreateCustomerUseCase` to ensure correct handling of payment term IDs during customer creation. - Validated behavior when no explicit payment term ID is provided. test: add unit tests for update customer use case - Developed tests for `UpdateCustomerUseCase` to verify payment term handling during customer updates. - Ensured that inactive payment terms are not assigned and that explicit null values are respected. feat: add dependency injection for customer company services - Implemented DI for customer company dependencies to facilitate service resolution. test: add tests for customer create data utility - Created tests for `buildCustomerCreateData` to validate payment term handling based on user input. |
||
|---|---|---|
| .ai | ||
| .vscode | ||
| apps | ||
| docs | ||
| modules | ||
| packages | ||
| scripts | ||
| tools | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| AGENTS.md | ||
| biome.json | ||
| Dockerfile | ||
| eslint.config.mjs | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| tsconfig.base.json | ||
| tsconfig.json | ||
| turbo.json | ||
ERP Monorepo
Monorepo del ERP con aplicaciones, módulos de dominio y paquetes compartidos.
El README raíz actúa como puerta de entrada del repositorio. La documentación funcional, operativa y arquitectónica vive en docs/README.md.
Estructura
apps/ aplicaciones ejecutables
modules/ módulos de negocio y backend
packages/ librerías compartidas
docs/ documentación operativa y arquitectónica
scripts/ utilidades de desarrollo
tools/ herramientas auxiliares del workspace
Áreas principales del workspace:
apps/web: frontend principal del ERP.apps/server: runtime servidor del monorepo.modules/*: módulos comoidentity,companies,customer-invoicesodocument-series.packages/*: utilidades compartidas comordx-ddd,rdx-utils,rdx-uiei18n.
Requisitos
- Node.js
>= 24 - PNPM
10.33.0
Primeros pasos
pnpm install
pnpm dev
Comandos frecuentes:
pnpm dev:server
pnpm dev:client
pnpm lint
pnpm check
pnpm typecheck
pnpm build
Documentación
- Índice general:
docs/README.md - Frontend:
apps/web/README.md - Identity:
modules/identity/README.md - Companies:
modules/companies/README.md - Auth legacy:
modules/auth/README.md
Forma de uso
- Usa este
READMEpara orientarte en el repositorio y arrancar el entorno. - Usa
docs/para contratos, decisiones de arquitectura, migraciones y runbooks. - Usa los
READMEde cada app o módulo para detalles locales de implementación.