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

fix(Message): Truncate very long names #298

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rebeccaalpert
Copy link
Member

Our API has name as optional - I'm letting it render as optional and then also adding truncation if it gets really long. We prioritize the timestamp at full width over the name right now - let me know if we want to prioritize the name over the timestamp instead.

Screenshot 2024-11-05 at 3 11 10 PM Screenshot 2024-11-05 at 3 10 50 PM Screenshot 2024-11-05 at 3 10 58 PM Screenshot 2024-11-05 at 3 10 26 PM

@rebeccaalpert rebeccaalpert linked an issue Nov 5, 2024 that may be closed by this pull request
@patternfly-build
Copy link

patternfly-build commented Nov 5, 2024

@@ -61,6 +61,13 @@ export default MessageLoading;
<Message name="Bot" role="bot" avatar={patternflyAvatar} content={orderedList} />
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can change "Example content with updated timestamp text" from the first bot message to be "Text-based message from a bot named "Bot", with updated timestamp"? Maybe sounds a little weird, but it could be good to point out that there's already a name with these messages, I tbh didn't notice myself in previous prs.

Longer term, I wonder if we could rename it to "FlyBot" or something, just to make it more "real" and obvious. Just a side comment/low priority thing

Copy link
Member Author

@rebeccaalpert rebeccaalpert Nov 7, 2024

Choose a reason for hiding this comment

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

I just pushed these changes. We did have this issue come up: #299. I think we do need improved docs around timestamps. I added a line about it, but let me know if you envision something else. I figure we can update the Message docs here as part of that, but I'll update our demo examples to include timestamps separately before I close #299.

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

Successfully merging this pull request may close these issues.

Limit length of chatbot name
3 participants