-
Notifications
You must be signed in to change notification settings - Fork 4
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
Improve notifications frontend #420
Conversation
[diff-counting] Significant lines: 88. |
|
||
return ( | ||
<Popup | ||
trigger={ | ||
<button className={styles.bell}> | ||
<button id="popup" className={styles.bell}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've already commented on this, but we should not be hardcoding id's within components. Maybe we can fix this after we migrate to modern React (18) where you get the useId
hook natively.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's fix master right now and reimplement it the right way later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your preview environment cornell-dti-carriage-web-pr-420 has been deployed. Preview environment endpoints are available at: |
Summary
Branching off of the previous popup aria tag fix pr, this pr improves the notifications design and implements view more functionality.
Note
This work is purely intuitive and is not based on any designs, so feel free to suggest any improvements or put it on hold until we have designs ready.
Test Plan
Home.-.Carriage.-.Brave.2023-03-08.01-40-58.mp4