Implement optional support for messages
Open
enhancement
- Dominant language
- Swift
- Stars
- 4.6k
- Forks
- 588
- PR merge metrics
- No merged PRs in 30d
Description
- Handle throwing gracefuly
- Define strategies for either not showing part of the content, or showing unsupported message if part couldn't be build
Contributor guide
Research direction
Start by tracing the message-building and display entry points in Chatto, since the issue names no files or tests. Clarify how failures should be handled and choose between omitting unsupported content or showing an unsupported-message notice; done means the selected behavior is implemented and verified for both successful and unsupported messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100