CLI edit and schedule silently truncate unquoted messages

Open Beginner friendly
#788 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
nodejs, typescript
Domain
cli

Research direction

Start in the CLI command handlers for vb edit and vb schedule and find where the message words are collected into an argument list; the bug is that extra words are dropped instead of rejected. Copy the validation that post and reply gained in PR #509 so both commands print a quote-the-message usage error and exit 2 before any write happens. Done means rerunning the issue's repro block shows status 2 for both commands and the stored message and schedule unchanged; run the existing CLI tests for edit, schedule, post and reply.

Written by the indexing model from the issue text.

Description

vb edit and vb schedule save only the first word of an unquoted multi-word message and exit 0. This overwrites the existing message or queues an incomplete one.

Reproduce on 0.54.0

With Node.js 22.18+ and npm, start a fresh local Board in one terminal.

npm exec --yes --package=@vercel/[email protected] -- vb serve --port 0 --no-inspect --dir "$(mktemp -d)"

In a second terminal, replace the BOARD_URL placeholder with the full URL printed by vb serve, then paste this block.

BOARD_URL='<URL printed by vb serve>' \
  npm exec --yes --package=@vercel/[email protected] -- sh <<'SH'
id=$(vb post notes original)

vb schedule notes status update --in 1d
echo "$?"  # 0
vb schedules  # Scheduled text is "status"

vb edit "$id" replacement complete message
echo "$?"  # 0
vb read "$id"  # Saved text is "replacement"
SH

Quoting the full message preserves all the words.

Expected behavior

Both commands should return usage status 2 and tell the caller to quote the full message before making any changes. post and reply already reject extra message arguments after #509.

Dominant language
TypeScript
Stars
178
Forks
16
Avg merge
8h 44m
Merged PRs (30d)
411

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/board

All issues in vercel/board

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.