- 
                Notifications
    You must be signed in to change notification settings 
- Fork 92
Description
Description
Issue Overview:
Upon setting up and initiating the server as per the provided documentation, I've noticed an inconsistency that affects the operation of the application. The server exclusively serves v2 endpoints, while the application consistently attempts to access v1 endpoints, resulting in 404 errors for every API call.
Expected Behavior:
The application should seamlessly integrate with the backend, with endpoint versions correctly aligned to ensure functionality.
Current Behavior:
Due to the mismatch in API versioning (backend on v2 and frontend on v1), all interactions between the front and backend are failing.
Steps to Reproduce:
- Follow the backend setup instructions exactly as specified in the README.
- Start the server and monitor the logs while interacting through the app.
- Notice that all backend calls from the app are attempting to access non-existent endpoints.
Request for Update/Clarification:
Could we have an update on the backend's migration to v2 endpoints? If the migration is intentional, I suggest either updating the frontend to match this change or providing a legacy support path for v1 endpoints to ensure continuity of service until the frontend can be updated.