google-labs-jules[bot] 57b913d135 Fix: Correct API endpoint pathing for expenses to resolve 404 errors ... The expenses frontend was encountering 404 errors due to mismatched API paths between the frontend calls and backend routing. This commit addresses the issue by: 1. Modifying backend API routing in `be/app/api/v1/api.py`: - Added a `/financials` prefix to the `financials.router`. Expense endpoints are now served under `/api/v1/financials/expenses`. 2. Updating frontend API configuration in `fe/src/config/api-config.ts`: - Prepended `/api/v1` to all paths within the `API_ENDPOINTS.FINANCIALS` object to match the new backend structure (e.g., `API_ENDPOINTS.FINANCIALS.EXPENSES` is now `/api/v1/financials/expenses`). 3. Updating frontend expense service in `fe/src/services/expenseService.ts`: - Replaced hardcoded relative URLs with the updated constants from `API_ENDPOINTS.FINANCIALS`. - Ensured `API_ENDPOINTS` is correctly imported. These changes align the frontend API calls with the backend endpoint definitions, resolving the 404 errors.		2025-06-03 10:04:42 +00:00
..
auth	feat: Implement refresh token functionality in authentication flow	2025-05-25 12:51:02 +02:00
v1	Fix: Correct API endpoint pathing for expenses to resolve 404 errors	2025-06-03 10:04:42 +00:00
__init__.py	weeee💃	2025-03-30 16:02:49 +02:00
api_router.py	weeee💃	2025-03-30 16:02:49 +02:00