My main reason for making this change would be to make it easier to develop the frontend on my local machine by supplying the entire backend via a proxy: conucourseplanner.online/courseplannerd/api. This is pretty easy to setup with nginx and I would be able to simply run the frontend build command (build-dev) to view my changes instead of having to wait for scp and tomcat's auto-reload to finish.
I also think its just generally a good idea to separate our api calls into a specific url "folder". It separates the frontend resources from the backend ones more clearly.
Description
Currently all of our backend api requests are performed on the root path of the website, like http://conucourseplanner.online/allsequences etc. I would like to move the entire api to be under the folder /api so the same request would instead look like: http://conucourseplanner.online/api/allsequences.
The benefits
My main reason for making this change would be to make it easier to develop the frontend on my local machine by supplying the entire backend via a proxy: conucourseplanner.online/courseplannerd/api. This is pretty easy to setup with nginx and I would be able to simply run the frontend build command (
build-dev
) to view my changes instead of having to wait forscp
and tomcat's auto-reload to finish.I also think its just generally a good idea to separate our api calls into a specific url "folder". It separates the frontend resources from the backend ones more clearly.