A user details attribute is available to track no-shows
Pull Request 1 introduces a Firebase Firestore User Details collection for storing primarily internally user-related information. Pull request 34 introduces a Firebase Firestore Event collection that may be used for storing information related to user-defined events that take place within the application.
Pull request 42 introduces a calendar page for scheduling to brainstorm around how event tracking could be implemented. Additional effort is needed to determine how a circumstance like a no-show should be represented, retrieved, and stored.
Acceptance criteria:
Pull Request 1 introduces a Firebase Firestore User Details collection for storing primarily internally user-related information. Pull request 34 introduces a Firebase Firestore Event collection that may be used for storing information related to user-defined events that take place within the application.
Pull request 42 introduces a calendar page for scheduling to brainstorm around how event tracking could be implemented. Additional effort is needed to determine how a circumstance like a no-show should be represented, retrieved, and stored.