Is your feature request related to a problem? Please describe.
currently, all API endpoints in the backend are hardcoded. This lead to the tight coupling between configs and code. Due to this with a single spelling mistake can cost huge debug hours. Also, If API endpoints will change in future, this will be a big problem. Because in a change, it needs to change in every place manually.
Describe the solution you'd like
YAML based route/config management service that can call in any place in the project.
Describe alternatives you've considered
I have considered the database based dynamic route/config management as well, but in this project YAML is the most suitable one.
Additional context
NO
Is your feature request related to a problem? Please describe.
currently, all API endpoints in the backend are hardcoded. This lead to the tight coupling between configs and code. Due to this with a single spelling mistake can cost huge debug hours. Also, If API endpoints will change in future, this will be a big problem. Because in a change, it needs to change in every place manually.
Describe the solution you'd like
YAML based route/config management service that can call in any place in the project.
Describe alternatives you've considered
I have considered the database based dynamic route/config management as well, but in this project YAML is the most suitable one.
Additional context
NO