-
Notifications
You must be signed in to change notification settings - Fork 0
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
collapsible items in univ home page and chapter requests #145
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
LGTM, the transitions look super nice! Tested resources, members, chapter info, and pending requests. Good job team!
tiles={userRequests.map((user, index) => { | ||
return ( | ||
<PendingCard | ||
key={index} |
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.
@nickbar01234 is it more safe to use user.uid as the key? I've had some problems when using the index for the key.
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.
Yep, I agree. In general, it's safer to not use index, as items in a list can be shifted / re-ordered. I think in this case, it's fine, because userRequests
are passed from the server, and we refresh the page every time. You can find more details here
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.
Changes are fantastic, thank you! After you guys fix the merge conflict, feel free to merge whenever.
tiles={userRequests.map((user, index) => { | ||
return ( | ||
<PendingCard | ||
key={index} |
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.
Yep, I agree. In general, it's safer to not use index, as items in a list can be shifted / re-ordered. I think in this case, it's fine, because userRequests
are passed from the server, and we refresh the page every time. You can find more details here
6ae1bd5
to
baa2c1b
Compare
Merging ahead for our sponsor meeting! |
No description provided.