SCS: Redo Folder Structure for API
What is the goal or the problem, and why is it important?
The goal of this issue is to have all files structured properly within the API of the Bear Necessities Market (BNM), named correctly, and in the correct location. This structure will be based on the existing GuestInfoSystem as outlined below.
How are you going to achieve the goal or solve the problem
The assignees of this task will work to structure the files in InventorySystem according to the existing file structure in GuestInfoSystem during this sprint (Sprint 2). This will include changes/edits such as file renaming, relocating files to new or correct folders, and creating any missing files or folder that need to be added for future use of the InventorySystem.
GuestInfoSystem API: https://gitlab.com/LibreFoodPantry/client-solutions/bear-necessities-market/guestinfosystem/guestinfoapi
A reference of the basics of file naming conventions for the sprint members to use/reference is this article: https://www.resourcespace.com/blog/file-naming-conventions
What will be produced due to this effort and where will it live on GitLab?
The InventorySystem API file structure will be changed to match that of the GuestInfoSystem API file structure. This will live in the API project.
Give a justification of weight or due date.
The weight that has been given to this task is a 4. Since this issue depends on the file structure of GuestInfoSystem and the restructuring of the 'System' as a whole, this issue will most likely take a whole week to do correctly.
Who will do it, and what will they do?
@CollinW77 & @anhprotien588 will work on this task while being overseen by @egartley. @CollinW77 & @anhprotien588 will continue improving navigation and editorial skills within GitLab, specifically the InventorySystem and GuestInfoSystem API being used for the BNM. This gives both team members a chance to understand the file structure at hand better and what might be next to work on in the API system being created. @egartley will serve as a guide for @CollinW77 and @anhprotien588, allowing both members to be frequently involved, while also being able to resolve questions in a timely manner so that it does not impact other team members and their assigned tasks.
What was the outcome?
The revised structure is available here https://gitlab.com/LibreFoodPantry/client-solutions/bear-necessities-market/inventorysystem/api