René's URL Explorer Experiment

Title: feat(cli): relative-time flags on generated commands' unix-seconds timestamps by ysyneu · Pull Request #47 · flashcatcloud/flashduty-cli · GitHub

Open Graph Title: feat(cli): relative-time flags on generated commands' unix-seconds timestamps by ysyneu · Pull Request #47 · flashcatcloud/flashduty-cli

X Title: feat(cli): relative-time flags on generated commands' unix-seconds timestamps by ysyneu · Pull Request #47 · flashcatcloud/flashduty-cli

Description: What Generated CLI commands forced raw unix integers on their time flags, while curated commands (incident list --since/--until) accepted ergonomic relative time (7d, now, dates). This closes that inconsistency — part of the generated-as-single-source convergence (Phase 2, after #46's generic table renderer). Every unix-SECONDS timestamp flag on a generated command now accepts: a duration — 7d, 24h (= now minus that) +7d for the future now a date / datetime / RFC3339 raw unix seconds (back-compatible — the old int form still works) …parsed at runtime via timeutil.Parse, the exact logic curated commands already use. How The generator (internal/cmd/cligen) detects unix-seconds timestamp fields and emits a string flag + a genParseTimeFlag pre-parse instead of an int flag. Detection is deliberately precise so it never corrupts a non-timestamp int: Field kind Example Treated as Why unix-seconds timestamp start_time, end_time, start, end, *_at_*_seconds relative-time string a point in time millisecond timestamp RUM/sourcemap/webhook start_time stays int64 Parse yields seconds → 1000× wrong duration delay_seconds, seconds_to_ack stays int64 a count of seconds, not a point in time Beyond the description-keyword signal (unix/epoch + second), two name conventions catch fields the spec under-documents — eliminating asymmetric start/end pairs: bare start/end window boundaries (schedule list --start was prose-only) the _at_*_seconds convention (close_at_seconds, created_at_start_seconds, created_at_end_seconds) — the _at_ point-in-time marker is what distinguishes these from a delay_seconds-style duration. Help stays consistent: both the cobra flag usage and the Long "Request fields" block render these as string + the accepted-forms hint. Verification go build/vet/test ./... green; gofumpt clean; new unit tests for the detector (incl. ms/duration exclusions + the deficient-field cases) and the runtime parse helper. Live testback E2E: incident post-mortem-list --created-at-start-seconds 30d --created-at-end-seconds now and insight account --start-time 7d --end-time now return data; raw-unix still works; invalid values error cleanly client-side (invalid --start: ...). Full e2e suite (-tags=e2e) vs base: zero new failures (138 pass / 27 pre-existing env fails / 6 skip — same set as base).

Open Graph Description: What Generated CLI commands forced raw unix integers on their time flags, while curated commands (incident list --since/--until) accepted ergonomic relative time (7d, now, dates). This closes that ...

X Description: What Generated CLI commands forced raw unix integers on their time flags, while curated commands (incident list --since/--until) accepted ergonomic relative time (7d, now, dates). This closes that ...

Opengraph URL: https://github.com/flashcatcloud/flashduty-cli/pull/47

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width