Open Issues Need Help
View All on GitHubAI Summary: This issue proposes refactoring the authentication logic for 'Plemsi' by creating a dedicated authentication table. This will decouple authentication data from the 'clientes' table and establish a foreign key relationship, ensuring better data integrity and maintainability. The task involves database schema changes, data migration, and updating relevant application code.
AI Summary: This issue requires refactoring the `InvoicesPendingWithDetails` endpoint to fetch client authentication details from a new table, `auth_plemsi_client`, instead of the current `client_billing_electronic` table. The lookup will change from `api_key` to a combination of `client_id` and `provider_type`, requiring conditional logic to select the correct authentication record.
AI Summary: This issue requires updating the billing endpoint to correctly consume a standardized, enveloped response from the `InvoicesPendingWithDetails` endpoint. The current implementation expects a flat array of invoices, but the new structure includes metadata and a `data` field containing the invoices. The change involves updating the DTOs and extracting the invoice array from the `data` property.
AI Summary: This issue proposes standardizing the API response structure for the `GET /api/v1/invoicespendingwithdetails` endpoint. Currently, it returns a flat array of invoices, but the goal is to wrap this array within a `data` field and include metadata like pagination information (`total`, `page`, `pageSize`, `totalPages`), a `success` boolean, and a `message` string. This change aims to align with modern RESTful API practices and improve performance by implementing pagination.