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

feat(fuselage): MessageEmoji and ThreadMessageEmoji components #709

Merged
merged 2 commits into from
May 2, 2022

Conversation

gabriellsh
Copy link
Member

Proposed changes (including videos or screenshots)

image
image

Issue(s)

Further comments

image,
children,
}: MessageEmojiBaseProps) => (
<div
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<div
<span

Because it could be children of <p>

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I changed it's display to be inline-block so this shouldn't cause problems, but I will change because it's more semantic. Thanks for the tip!

Comment on lines +23 to +24
'rcx-message__emoji',
className,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'rcx-message__emoji',
className,
className && 'rcx-message__emoji',
className,

Can we add a conditional here? cause when the className is undefined we will render the emoji text like :random-text: so we don't need the emoji style in this scenario.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also we need the name in the class name to render the correct style of emoji

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kind of agree with the first comment. I know we need for this to be "sizeless" whenever the emoji doesn't exist, but not sure if we should depend on the className. For ex: if for some reason we decide to pass another className, this implementation falls apart. Maybe we need an aditional prop?

On the second one, I don't se a reason to add the name in the className, because that is Application specific. If the application needs to send the name as a className, it can do so by including it in the className prop.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized that for the first comment, we can just not use this component :p. I'll leave it like it is...

filipemarins
filipemarins previously approved these changes Apr 29, 2022
@gabriellsh gabriellsh merged commit 2b224b0 into develop May 2, 2022
@gabriellsh gabriellsh deleted the new/messageEmoji branch May 2, 2022 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants