During this semester, functionality was not in focus, but instead refactoring the code base, to make a better experience for the future semesters.
During the refactorization of the web-api, several finds indicated that some functionality was left unused. For instance, remnants of a logging feature no longer being used, as well as a week-template controller, that is not being used by the weekplaner, despite it might add value.
For reference, the logging is removed from the repository, while the template controller is kept, as it might provide value in the future.
These finds give motivation for examining if there are more such remnants. Specifically, we suggest that all endpoints are examined to determine if they are being used, and if not, if they are supposed to be used. This should also allow for a general insight into parts of both the web-api and frontend, without calling for code modifications.
Possible Suggested Solution
Go through all endpoints and establish if, and from where they are called on the frontend.
If some endpoints are not being utilized, establish with the other groups of the semester, if they should in fact be utilized somewhere in the frontend, of if it should be deleted from the backend.
Description
During this semester, functionality was not in focus, but instead refactoring the code base, to make a better experience for the future semesters.
During the refactorization of the web-api, several finds indicated that some functionality was left unused. For instance, remnants of a logging feature no longer being used, as well as a week-template controller, that is not being used by the weekplaner, despite it might add value. For reference, the logging is removed from the repository, while the template controller is kept, as it might provide value in the future.
These finds give motivation for examining if there are more such remnants. Specifically, we suggest that all endpoints are examined to determine if they are being used, and if not, if they are supposed to be used. This should also allow for a general insight into parts of both the web-api and frontend, without calling for code modifications.
Possible Suggested Solution