You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our backend currently has hardcoded endpoints for specific indexes. As we're adding more indexes, this setup will be hard to maintain. We need a flexible endpoint system that can handle different indexes based on the request details, without needing hardcoded paths for each one.
Tasks
Review the existing endpoint implementations.
Design a generic endpoint system that can dynamically adjust to handle different indexes based on input parameters such as index type or name.
Implement the new endpoint system, ensuring it supports all existing functionalities and can easily scale to include new indexes.
Test the new endpoint system.
Update all relevant documentation and API usage guides.
Acceptance Criteria
The backend must dynamically adapt its endpoints to handle requests for any specified index without hardcoding for specific indexes.
The new system must maintain all existing endpoint functionalities and seamlessly integrate new indexes.
The text was updated successfully, but these errors were encountered:
k-allagbe
changed the title
As indexes are multiplying, we need to manage our endpoints and env variables in a generic way in finesse-backend
Refactor search endpoints in finesse-backendMay 6, 2024
k-allagbe
changed the title
Refactor search endpoints in finesse-backend
As our Index List is Expanding, Refactor search endpoints in finesse-backendMay 6, 2024
k-allagbe
changed the title
As our Index List is Expanding, Refactor search endpoints in finesse-backend
Refactor Endpoint Management to Support Multiple Indexes Dynamically in finesse-backendMay 6, 2024
k-allagbe
changed the title
Refactor Endpoint Management to Support Multiple Indexes Dynamically in finesse-backend
Refactor Endpoints to Support Multiple Indexes Dynamically in finesse-backendMay 6, 2024
Description
Our backend currently has hardcoded endpoints for specific indexes. As we're adding more indexes, this setup will be hard to maintain. We need a flexible endpoint system that can handle different indexes based on the request details, without needing hardcoded paths for each one.
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: