Skip to content

feat(status): set a status with only an emoji - #123

Merged
scottlovegrove merged 1 commit into
mainfrom
scottl/emoji-only-status-updates
Nov 17, 2026
Merged

scottlovegrove merged 1 commit into
mainfrom
scottl/emoji-only-status-updates

Conversation

@scottlovegrove

Copy link
Copy Markdown
Collaborator

Short description

The API now accepts a status with an emoji and no message (@todoist/comms-sdk 5.2.2, already pinned, types message as optional and nullable). #122 taught tdc status to show such a status; this lets tdc status set create one.

  • tdc status set <message> becomes tdc status set [message]. Leaving the message out sends message: null, the same way set already clears an omitted emoji, expiry or pause flag: tdc status set --emoji 🤒 --for 1d.
  • With neither a message nor --emoji, the command fails with MISSING_CONTENT ("A status needs a message, an emoji or both") before calling the API, with both forms as hints.
  • An explicit empty message (tdc status set "" --emoji 🤒) is still rejected, consistent with --emoji '' and --until '', and now hints to leave the message out instead.
  • --dry-run shows Message: cleared when it is left out. Text output is Status set: 🤒; --json gives {"status":{"message":null,"emoji":"🤒"}}.
  • Help text, SKILL_CONTENT and skills/comms-cli/SKILL.md say a status needs a message, an emoji or both, with an emoji-only example.

Evidence

  • Six new tdc status set tests (payload sent to the API, text, JSON and dry-run output, MISSING_CONTENT with and without other flags, the empty-message hint) failed before the change and pass after it. All 74 status tests pass.
  • The built CLI prints the dry-run preview, the MISSING_CONTENT error (text and --json) and the empty-message hint as described above.
  • npm run verify passes.
  • Not run against the real API: setting a status changes the account's real status, which is shared with Todoist.

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.
@scottlovegrove scottlovegrove self-assigned this Nov 17, 2026
@scottlovegrove scottlovegrove added the 🚢 Ship PR requires passing checks before merge, but no independent human review. label Nov 17, 2026
@scottlovegrove

Copy link
Copy Markdown
Collaborator Author

@lmjabreu Tagging you only for info purposes.

@scottlovegrove
scottlovegrove merged commit c8c939e into main Nov 17, 2026
5 of 6 checks passed
@scottlovegrove
scottlovegrove deleted the scottl/emoji-only-status-updates branch November 17, 2026 11:34
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))
@doist-release-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 5.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

released 🚢 Ship PR requires passing checks before merge, but no independent human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant