Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Notification Page Functionality (Frontend) #36

Closed
h0ethan04 opened this issue Feb 4, 2024 · 2 comments · Fixed by #39
Closed

Complete Notification Page Functionality (Frontend) #36

h0ethan04 opened this issue Feb 4, 2024 · 2 comments · Fixed by #39
Assignees
Labels

Comments

@h0ethan04
Copy link
Contributor

h0ethan04 commented Feb 4, 2024

Instructions

The individual notification component has been completed, now it's time to assemble the entire window.
There are two things displayed in the notifications center: pending accounts and events recently added to the Published Schedule. This task has an associated backend task (see #45 on backend). For the frontend, this task requires the following:

  • Admin users should be able to see pending user accounts and recently created Published Schedule events
  • Notification window should group pending user accounts by date of creation
  • Display Published Schedule events created in the last week
  • Display Published Schedule events marked as confirmed in the last week

Notes

  • If you have any questions about designs talk to Selina

Acceptance Criteria

  • Notifications are now displayed by day
  • Approving an account adds a notification indicating the user was approved
  • Newly confirmed events in the Published Schedule show up as notifications
  • Adding events to the published schedule result in a notification

Resources

Notifications Center Figma
Notifications Page Component
Chakra-UI docs

@seancfong
Copy link
Member

Notification window should group pending user accounts by date of creation.

@h0ethan04 The users table currently doesn't have a creation date column. Do you know when the schema will be updated for this task?

@h0ethan04
Copy link
Contributor Author

h0ethan04 commented Feb 18, 2024

That's currently part of the backend task, the column name is approved_on. I think we had decided that when a new user is created the approved_on column would initially store the creation date then get overwritten once the account is approved. @seancfong

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants