fix(tugasna): correct CLI help text to match the API#91
Merged
Conversation
The `sawala tugasna` help strings drifted from the Tugasna API:
- comment create/update documented the body as { body }; the server field is
{ text } (plus optional { parentId } to reply).
- item move documented { statusId?, position? }; both are required.
- backlog place documented statusId as optional; it is required.
- item create/update didn't note that startDate/dueDate are epoch-ms numbers,
not date strings.
Help text only — the CLI still passes the --data/--file body through verbatim,
so no request behaviour changes. Adds a patch changeset.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QGdUAa2d3N3vDXrtLB7ZKM
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.
Summary
Fixes help-text drift in the
sawala tugasnacommand group found during smoke testing. Help strings only — the CLI still passes the--data/--filebody through verbatim, so no request behaviour changes.comment create/comment update{ body }{ text }(server field),+ { parentId }to replyitem move{ statusId?, position? }{ statusId, position }— both requiredbacklog place{ boardId, statusId?, position? }statusIdrequireditem create/item updatestartDate/dueDateare epoch-ms numbers, not date stringsThese match the Tugasna route schemas (
TextBody = { text },MoveBody = { statusId, position },PlaceBodywith requiredstatusId, and epoch-msz.number().int()dates).Testing
npm run -w @sawala/cli typecheck— passesnpm run -w @sawala/cli test— 133 tests pass (existing tugasna tests assert paths/methods/bodies, unaffected by help-string changes)Changeset
.changeset/tugasna-help-fixes.md—@sawala/clipatch.🤖 Generated with Claude Code
https://claude.ai/code/session_01QGdUAa2d3N3vDXrtLB7ZKM
Generated by Claude Code