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
Add reactions to meetings. Rewrote meeting from class component -> hook. #3548
Conversation
jonasdeluna
commented
Feb 10, 2023
Cool! 💯 We can use this to register who wants pizza for our meetings haha! Thought; could we perhaps move it down to the comment section? I feel like the sidebar is only for general info + admin stuff. |
2d808a6
to
4e2addc
Compare
|
It does sort of make sense for it to be in the original position (ref #3548 (comment)) to make it clear it's part of the meeting response, and not a reaction on the meeting itself? |
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.
Awesome! 🍕
Also, small tip; your commit could have been split into two separate ones for easier code review.
4e2addc
to
6eb1282
Compare
^removed & placed emojis at the bottom
|
6eb1282
to
b54a2cb
Compare
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.
Cool, this is a super-nice feature and as mentioned could be useful for more than just fun :)/ Just some questions :)
I also liked having the reactions someplace more visible than under the content, as I feel they "disappear" if you have just a little text in the meeting
) => (loggedIn ? dispatch(fetchMeeting(meetingId)) : Promise.resolve()); | ||
) => | ||
loggedIn | ||
? dispatch(fetchMeeting(meetingId), fetchEmojis()) |
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.
Are you sure you can dispatch like this? According to the docs, this is not an option.
You could rather do a Promise.all([dispatch(fetchmeeting(...)), dispatch(fetchemojis())]
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.
Also, why are you fetching emojis here and passing fetchEmojis
into the reaction picker?
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.
Hmm I'm not entirely sure actually. It was written that way in the ArticleDetailRoute.tsx file, but I'll try the promise.all instead. When not fetching he emojis and passing them the emojipicker component doesn't load properly (at all)
b54a2cb
to
5177761
Compare
@LudvigHz |
Yeah, I agree. And it is a bit annoying sometimes that comments are all the way at the bottom, but on the other hand, comments don't really fit anywhere else, whereas reactions can fit in a small space almost anywhere, so it's more flexible where we can put it |
5177761
to
e62bfd0
Compare
Could not reproduce the cypress fail, but may be due to lack of the correct backend version? |
d0e93be
to
7bab568
Compare
7bab568
to
7bcbfb9
Compare
@@ -9,7 +9,7 @@ | |||
} | |||
|
|||
.statistic { | |||
font-size: 2.2rem; | |||
font-size: 1.2rem; |
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.
What is this?
@@ -56,7 +56,7 @@ div > .locationContainerItem { | |||
|
|||
.contactTitle { | |||
color: var(--lego-font-color); | |||
font-size: 1.7rem; | |||
font-size: 1rem; |
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.
What does this do and why is it part of this PR?
7bcbfb9
to
c9cdb73
Compare