Repository navigation
fix(status): show a status that has only an emoji - #122
Merged
Merged
Conversation
A status can now be just an emoji, and the API returns it with a null message. @todoist/comms-sdk 5.0.1 rejected that response outright, so one user with an emoji-only status broke every command that loads workspace users, including `tdc thread view`. @todoist/comms-sdk 5.2.2 accepts it, and formatStatus now joins the emoji and message it has, instead of printing "🎯 null".
doistbot
reviewed
Nov 17, 2026
doistbot
left a comment
Member
There was a problem hiding this comment.
This PR updates fix(status): show a status that has only an emoji. No issues were flagged in the reviewed diff.
doist-release-bot Bot
added a commit
that referenced
this pull request
Nov 17, 2026
## [5.0.3](v5.0.2...v5.0.3) (2026-11-17) ### Bug Fixes * **status:** show a status that has only an emoji ([#122](#122)) ([51d09f6](51d09f6))
Contributor
|
🎉 This PR is included in version 5.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Short description
A Comms status can now be just an emoji, and the API returns it with
message: null.@todoist/comms-sdk5.0.1 rejected that response with aZodError, so a single user with an emoji-only status broke every command that loads workspace users.tdc thread viewfails on any thread in that workspace, for example.@todoist/comms-sdkfrom 5.0.1 to 5.2.2, which accepts a status without a message (fix(users): accept a user status without a message comms-sdk-typescript#153, #154). The versions in between are additive or unrelated fixes; the OAuth changes (#151, #152) touchgetAuthorizationUrl, which the CLI does not use.formatStatusjoins whichever of the emoji and message the status has, sotdc statusandtdc userprint🎯instead of🎯 null.Setting an emoji-only status (
tdc status setstill requires a message) is left for a separate change.Evidence
tdc status showcases for an emoji-only status (message null, absent, and null with a pause) failed before the fix with🎯 null/🎯 undefinedand pass after it.npm run verifypasses.