SCS: Update API to Match Back-End Schema
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
As the back end gets updated with the correct schemas, the API will need to be updated in response. It is important to maintain parity between these two systems, considering how tightly coupled they are.
Epic: &2 (closed)
Issues:
- Redo Folder Structure (Back End)
- Redo Folder Structure (API)
- Integration with Front End & Back End
- https://gitlab.com/LibreFoodPantry/client-solutions/bear-necessities-market/inventorysystem/api/-/issues/new
How are you going to achieve the goal or solve the problem?
This task will include the creation, deletion and modification of existing routes within the current API system.
What will be produced as a result of this effort and where will it live on GitLab?
All new files generated in relation to these schema / route changes will be hosted in the API project. Any documentation changes related will appear in the documentation project.
Give a justification of weight or due date.
Weight: 4
Due Date: 04/01/2023
Justification: This is one of the final steps for this project's implementation and therefore must wait until all other tasks related to it are completed. The client-side data distributed by the API may evolve differently than the raw data stored in the Back End, and so there may be additional, unseen discrepancies with how we format the API.
Who will do it, and what will they do?
We will use this as an opportunity to help @anhprotien588 learn about the API and how it works in relation to the data from the Back End. @GowersCam will be assigned as support. Together, they will work to keep the API up-to-date with the Back End, implementing or modifying any routes that need it. Then, they will verify all routes in the API work as intended.
What was the outcome?
The outcome of this issue is abandonment and mark for closing. The reason this was abandoned because of a redefined task definition and sprint change. The new task is at https://gitlab.com/LibreFoodPantry/client-solutions/bear-necessities-market/inventorysystem/api/-/issues/new