Repository navigation
feat(status): set a status with only an emoji - #123
Merged
Merged
Conversation
The API now accepts a status with an emoji and no message, so the message argument to `tdc status set` becomes optional. Leaving it out sends `message: null`, matching how `set` already clears an omitted emoji, expiry or pause flag. A status still needs a message, an emoji or both: with neither, the command fails with MISSING_CONTENT before calling the API. An explicit empty message is still rejected, now with a hint to leave it out.
Collaborator
Author
|
@lmjabreu Tagging you only for info purposes. |
doist-release-bot Bot
added a commit
that referenced
this pull request
Nov 17, 2026
## [5.1.0](v5.0.3...v5.1.0) (2026-11-17) ### Features * **status:** set a status with only an emoji ([#123](#123)) ([c8c939e](c8c939e))
Contributor
|
🎉 This PR is included in version 5.1.0 🎉 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
The API now accepts a status with an emoji and no message (
@todoist/comms-sdk5.2.2, already pinned, typesmessageas optional and nullable). #122 taughttdc statusto show such a status; this letstdc status setcreate one.tdc status set <message>becomestdc status set [message]. Leaving the message out sendsmessage: null, the same waysetalready clears an omitted emoji, expiry or pause flag:tdc status set --emoji 🤒 --for 1d.--emoji, the command fails withMISSING_CONTENT("A status needs a message, an emoji or both") before calling the API, with both forms as hints.tdc status set "" --emoji 🤒) is still rejected, consistent with--emoji ''and--until '', and now hints to leave the message out instead.--dry-runshowsMessage: clearedwhen it is left out. Text output isStatus set: 🤒;--jsongives{"status":{"message":null,"emoji":"🤒"}}.SKILL_CONTENTandskills/comms-cli/SKILL.mdsay a status needs a message, an emoji or both, with an emoji-only example.Evidence
tdc status settests (payload sent to the API, text, JSON and dry-run output,MISSING_CONTENTwith and without other flags, the empty-message hint) failed before the change and pass after it. All 74 status tests pass.MISSING_CONTENTerror (text and--json) and the empty-message hint as described above.npm run verifypasses.