Contributions
See here (at the bottom) for my contributions.
Frontend Button Functions
This week I mainly focused on frontend since my api is basically complete (from the earlier work days this week). So I created a basic framework of the user inputs, updated the stars, and I included some css to represent how I want the overall score card to look. See the photo below.
Validation
I found validation for my portion to be very difficult to figure out. After doing alot of research I found built in ways to include validations that would be easily used to have the data assigned and stored properly once the backend and frontend are connected.
I decided that the built in would be better than manually creating functions to check the validations for a few reasons:
1) Less time consuming (obviously)
2) Easily implemented
3) Ways to retain and store data should be simpler through auto validation. Planning to use sqlite db
Here are some of the conditions that are included with the html forms val:
All fields must be filled in.
Email must include @ symbol, with phrase before and after symbol
Plan for Next Week
My plan for next week is connecting the front and backend endpoints. This is important because the front and back end are now basically complete individually. But in order for the program to be successful, both must communicate data with each other: the front end presenting UI and receiving data, while the backend is updated. Here's the backend so far:
I am not completely done with front end however. This biggest thing I want to add after the connection of front and back end, is a function that calculates the average review. however this is only possible once data base is connected so I am saving this for the end (hopefully it shouldn't take too long)
Contributions See here (at the bottom) for my contributions.
Frontend Button Functions This week I mainly focused on frontend since my api is basically complete (from the earlier work days this week). So I created a basic framework of the user inputs, updated the stars, and I included some css to represent how I want the overall score card to look. See the photo below.
Validation I found validation for my portion to be very difficult to figure out. After doing alot of research I found built in ways to include validations that would be easily used to have the data assigned and stored properly once the backend and frontend are connected.
I decided that the built in would be better than manually creating functions to check the validations for a few reasons: 1) Less time consuming (obviously) 2) Easily implemented 3) Ways to retain and store data should be simpler through auto validation. Planning to use sqlite db
Here are some of the conditions that are included with the html forms val:
Plan for Next Week My plan for next week is connecting the front and backend endpoints. This is important because the front and back end are now basically complete individually. But in order for the program to be successful, both must communicate data with each other: the front end presenting UI and receiving data, while the backend is updated. Here's the backend so far:
I am not completely done with front end however. This biggest thing I want to add after the connection of front and back end, is a function that calculates the average review. however this is only possible once data base is connected so I am saving this for the end (hopefully it shouldn't take too long)
SCRUM Board SCRUM Board linked here.
Big Idea 5.3 and 5.4 Notes Notes