feat(add): support --daystamp for adding datapoints by narthur · Pull Request #221 · PinePeakDigital/buzz

narthur · 2026-01-27T14:28:52Z

Add optional --daystamp flag to the buzz add command and propagate it
through the datapoint creation path so callers can specify the datapoint
date instead of using the current timestamp.

Update CLI help and usage text to include --daystamp and document
YYYYMMDD format and ordering rules.
Parse and validate the --daystamp flag in the add command; print a
helpful error and exit on invalid format.
Preserve previous behavior by using the current timestamp when no
daystamp is provided.
Add CreateDatapointWithDaystamp wrapper and forward CreateDatapoint to
it (keeping compatibility); call the new function with the validated
daystamp when creating datapoints.
Enhance success messages to include the daystamp when supplied.

This allows users and scripts to add datapoints for specific dates (e.g.
backfilling) while maintaining idempotency via requestid.

Summary by CodeRabbit

New Features
- Added an optional --daystamp flag to buzz add to submit datapoints for a specific date (YYYYMMDD); success messages include the daystamp when provided.
Documentation
- README and CLI help updated with --daystamp usage, format, examples, and revised command signature.
Bug Fixes
- Improved detection and messaging for misplaced flags and added daystamp input validation.
Tests
- Added tests covering daystamp handling and misplaced-flag scenarios.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2026-01-27T14:29:13Z

📝 Walkthrough

Walkthrough

Adds optional daystamp support for datapoint submission: new exported CreateDatapointWithDaystamp that prefers daystamp over timestamp, CLI parsing/validation for a --daystamp flag in buzz add, updated tests, docs, and misplaced-flag detection.

Changes

Cohort / File(s)	Summary
Core API `beeminder.go`	Adds `CreateDatapointWithDaystamp(config *Config, goalSlug, timestamp, daystamp, value, comment, requestid string) error`; refactors `CreateDatapoint` to delegate to it. Payload uses `daystamp` when non-empty, otherwise `timestamp`.
CLI `main.go`	Adds `--daystamp` (YYYYMMDD) flag to `buzz add`, validates format, carries `daystampForAPI` into `CreateDatapointWithDaystamp`, and updates messages and misplaced-flag handling.
Documentation `README.md`	Updates `buzz add` usage and examples to include optional `--daystamp=<date>` (YYYYMMDD) and documents behavior when omitted.
Tests `beeminder_test.go`	Adds `TestCreateDatapointWithDaystamp` validating request form uses `daystamp` when provided and `timestamp` when omitted; checks `auth_token` and `value` fields.
Utilities `utils.go`, `utils_test.go`	`detectMisplacedFlag` now checks a knownFlags list including `--requestid` and `--daystamp`; tests expanded with cases involving `--daystamp` and multiple flags.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

feat: add 'buzz add' command to add datapoints without opening TUI #79: Overlaps CLI flow and datapoint-creation callsite changes affecting buzz add.
feat: add buzz refresh command for autodata refresh #138: Modifies CreateDatapoint/beeminder API logic; related to payload and API-call refactor.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title "feat(add): support --daystamp for adding datapoints" accurately summarizes the main change: adding a new --daystamp flag to the add command for specifying datapoint dates.
Docstring Coverage	✅ Passed	Docstring coverage is 90.91% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

github-actions · 2026-01-27T14:29:28Z

🚀 Pre-release Build Ready

Test builds are ready! Install directly using the bin command:

# Install the pre-release
bin install https://github.com/PinePeakDigital/buzz/releases/tag/pr-221-latest buzz-pr-221

# Run the pre-release
buzz-pr-221

# Uninstall the pre-release
bin remove buzz-pr-221

Direct Download Links

Or download binaries directly from the pre-release page:

💡 No GitHub login required for downloads!

🗑️ This pre-release will be automatically deleted when the PR is closed.

Copilot

Pull request overview

Adds support for an optional --daystamp flag to buzz add, allowing callers to create datapoints for a specific date (YYYYMMDD) while preserving existing behavior when the flag is omitted.

Changes:

Extend buzz add CLI parsing/help/usage to accept and validate --daystamp=YYYYMMDD.
Add CreateDatapointWithDaystamp API wrapper and route existing CreateDatapoint through it for backward compatibility.
Add unit tests verifying request payload uses daystamp when provided, otherwise timestamp.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
main.go	Adds `--daystamp` flag parsing/validation and updates help/usage + success output.
beeminder.go	Introduces `CreateDatapointWithDaystamp` and updates datapoint creation payload selection logic.
beeminder_test.go	Adds tests ensuring `daystamp` vs `timestamp` is correctly included in POST body.

main.go

Add optional --daystamp flag to the `buzz add` command and propagate it through the datapoint creation path so callers can specify the datapoint date instead of using the current timestamp. - Update CLI help and usage text to include --daystamp and document YYYYMMDD format and ordering rules. - Parse and validate the --daystamp flag in the add command; print a helpful error and exit on invalid format. - Preserve previous behavior by using the current timestamp when no daystamp is provided. - Add CreateDatapointWithDaystamp wrapper and forward CreateDatapoint to it (keeping compatibility); call the new function with the validated daystamp when creating datapoints. - Enhance success messages to include the daystamp when supplied. This allows users and scripts to add datapoints for specific dates (e.g. backfilling) while maintaining idempotency via requestid.

Update the "buzz add" usage and examples to include an optional --daystamp flag and document its format, default behavior, and use cases. Adjust the CLI synopsis so --daystamp and --requestid appear before the positional <goalslug> and <value> arguments. Why: - Users need a way to add datapoints for a specific date (backfill or pre-entry) without relying on current timestamp behavior. - Documenting the YYYYMMDD format and giving an example reduces user errors and support questions. - Moving optional flags before positionals makes the invocation clearer and matches how the tool parses those options.

Extend detectMisplacedFlag to recognize more than just --requestid. Introduce a knownFlags list (including --daystamp) and check each arg against all known flags, returning the first match. Update warning text in main so the usage example includes --daystamp. Expand unit tests to cover --daystamp detection, value forms (e.g. --daystamp=YYYYMMDD), and interactions when both --daystamp and --requestid are present to ensure the first flagged item is returned. These changes improve user feedback when flags are placed after positional arguments and prevent silent misinterpretation of flag-like inputs.

Update help text describe the default --daystamp "current time" instead of "today". This clar that the flag accepts full date in YYYYMMDD format and that the fallback is the current system time, which reduces ambiguity for users running the CLI in different timezones or contexts.

coderabbitai

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@main.go`:
- Line 830: Update the usage message printed by the fmt.Fprintf call that writes
to os.Stderr so the flag order matches the help text; change the format string
from "buzz add [--daystamp=DATE] [--requestid=ID] goalslug value comment" to use
"--requestid" before "--daystamp" (e.g., "buzz add [--requestid=ID]
[--daystamp=DATE] goalslug value comment") so all examples are consistent with
the help output.

In `@README.md`:
- Line 226: The README example places the flag after positional args which
contradicts the program's documented/implemented behavior (see
printAddUsageAndExit and handleAddCommand); update the example so flags precede
positional arguments (e.g., move --daystamp=20240115 before the positional
"exercise 1") and ensure the usage line matches the warning in handleAddCommand
and printAddUsageAndExit.

main.go

README.md

Copilot AI review requested due to automatic review settings January 27, 2026 14:28

Copilot started reviewing on behalf of narthur January 27, 2026 14:29 View session

Copilot AI reviewed Jan 27, 2026

View reviewed changes

main.go Show resolved Hide resolved

main.go Outdated Show resolved Hide resolved

narthur added 4 commits January 27, 2026 10:09

narthur force-pushed the daystamp-arg branch from a9adcae to e53a87a Compare January 27, 2026 15:09

coderabbitai bot reviewed Jan 27, 2026

View reviewed changes

main.go Outdated Show resolved Hide resolved

README.md Outdated Show resolved Hide resolved

narthur added 2 commits January 27, 2026 10:16

fix(cli): consistent flag ordering in usage examples

3f5c17d

docs(readme): place flags before positional arguments in examples

5ba2693

narthur merged commit 4f7ff34 into main Jan 27, 2026
5 checks passed

narthur deleted the daystamp-arg branch January 27, 2026 15:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(add): support --daystamp for adding datapoints#221

feat(add): support --daystamp for adding datapoints#221
narthur merged 6 commits intomainfrom
daystamp-arg

narthur commented Jan 27, 2026 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Jan 27, 2026 •

edited

Loading

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

github-actions bot commented Jan 27, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

coderabbitai bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

narthur commented Jan 27, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

github-actions bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Pre-release Build Ready

Direct Download Links

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

narthur commented Jan 27, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jan 27, 2026 •

edited

Loading

github-actions bot commented Jan 27, 2026 •

edited

Loading