You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the qr code functionality is complete, there are some oddities in its behaviors that we need to clean up.
READ ALL INSTRUCTIONS BEFORE STARTING
Note:
When working on the frontend, we want to work from making sure the site is responsive starting from a mobile device (this will make it easier when we modifying the styling for bigger screens)
When checking how the frontend looks on a mobile device through chrome's inspect element, be sure to select iPhone SE for test!!!
Heads up:
Feel free to utilize /client/src/components/playground/Playground.jsx to test out anything before putting it in their respective pages, or if there currently is no respective page
When prompted to log in, you can sign in with the account:
qr code should be moved into Teacher view components; make sure it shows up in the Teacher class and Teacher event modals in the /src/components/bookings directory of our frontend
checking in for classes using the qr code leads to too many entries in the table; there are two new entries in the table instead of one. Eliminate the extra post request, and ensure that students can only check in for a "scheduled class" once.
event checkins make a post request, but since events are a single occurrence we can just change to a put request and modify the existing entry in the table. Additionally, similar to the classes, we also have the bug of multiple post requests being sent and excessive entries in the table.
Notes
Acceptance Criteria
Resolves all bugs without introducing new unintended behaviors
Matches hi-fi structure (you can ignore coloring for now)
qr code is properly placed into teacher view components and does not show up on the student side
Resources
The text was updated successfully, but these errors were encountered:
Description
While the qr code functionality is complete, there are some oddities in its behaviors that we need to clean up.
READ ALL INSTRUCTIONS BEFORE STARTING
inspect element
, be sure to selectiPhone SE
for test!!!Feel free to utilize
/client/src/components/playground/Playground.jsx
to test out anything before putting it in their respective pages, or if there currently is no respective pageWhen prompted to log in, you can sign in with the account:
student:
teacher:
admin:
Instructions
/src/components/bookings
directory of our frontendNotes
Acceptance Criteria
Resources
The text was updated successfully, but these errors were encountered: