Final Individual Review
February 2024 (375 Words, 3 Minutes)
Project overview
Let ‘em Cook! is our own twist on a childhood favorite game of Little Alchemy. Instead of combining elements, we combine foods! We also have a leaderboard and trading features between users as well as a shop
My feature
My feature is the trading feature between users. When a user wants to trade with another, they must first send them a friend request and wait for the other user to accept before sending items to each other. This is done through the sqlite.db which contains every user’s list of friends and friend requests
College Board Requirements:
- Instructions for input from one of the following: the user (including user actions that trigger events), a device, an online data stream, a file
- Use of at least one list (or other collection type) to represent a collection of data that is stored and used to manage program complexity and help fulfill the program’s purpose
- At least one procedure that contributes to the program’s intended purpose, where you have defined the procedure’s name, the return type (if necessary), and one or more parameters
- An algorithm that includes sequencing, selection, and iteration that is in the body of the selected procedure
- Calls to your student-developed procedure
- Instructions for output (tactile, audible, visual, or textual) based on input and program functionality
Instructions for input from one of the following: the user (including user actions that trigger events), a device, an online data stream, a file
My part allows you to send a recipe to a friend using a form and then a button to send/accept friend requests
Use of at least one list (or other collection type) to represent a collection of data that is stored and used to manage program complexity and help fulfill the program’s purpose
Lists of a user’s friends in the sqlite.db allow for sending of items between friends
At least one procedure that contributes to the program’s intended purpose, where you have defined the procedure’s name, the return type (if necessary), and one or more parameters
parameter(self), returns if error, name(delete)
An algorithm that includes sequencing, selection, and iteration that is in the body of the selected procedure
The algorithmn first confirms the user did not send to themself before adding the friend request (sequencing), it selects the correct user based on the sender in the body (selection) after iterating throughout all of the users
Calls to your student-developed procedure
Frontend fetch request to backend calls to the delete function
Instructions for output
Code to generate the data tables
Key commits:
- Database fetch request This code helps create the tables by fetch request (GET) by iterating through the user’s list of friends, items, and all of the users and then appending to the correct lists to be explained
- Code logic for accepting friend request This backend code handles what happens when the frontend sends a DELETE request when clicking the button to accept friend request.
- Link to frontend pull requests
- Link to backend pull requests