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

Track error when message cannot be rendered #5739

Closed
Anderas opened this issue Mar 3, 2022 · 0 comments · Fixed by #5740
Closed

Track error when message cannot be rendered #5739

Anderas opened this issue Mar 3, 2022 · 0 comments · Fixed by #5740
Assignees
Labels
A-Timeline T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@Anderas
Copy link
Contributor

Anderas commented Mar 3, 2022

Your use case

If EventFormatter fails to return attributedString to render a message, the error is not tracked and message is not shown, leading to the issue that messages appear lost #5374.

There is a variety of reasons why why the creation of attributedStrings can fail, but without logs it is very difficult to determine the reason.

To solve this:

  • log error whenever an event cannot be converted to attributedString
  • display "unable to render" message, so that the user is aware a message is now missing

Have you considered any alternatives?

No response

Additional context

No response

@Anderas Anderas added T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements A-Timeline labels Mar 3, 2022
@Anderas Anderas self-assigned this Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Timeline T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant