bug(calendar): --cal and --calendars reject primary and email addresses that the positional calendarId accepts

Open Beginner friendly
#1,283 1 comment 1 reaction 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
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Read the strict lookup in internal/cmd/name_resolution.go and compare it with the positional path at lines 130–137 and the freebusy short-circuit in calendar_util.go. Reproduce with the commands in the issue, then verify that --cal primary and --cal [email protected] work, including together as --cal primary,[email protected].

Written by the indexing model from the issue text.

Description

clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2

Summary

gog calendar events primary and gog calendar events [email protected] work, but --cal primary and --cal <address of a calendar not in the calendar list> fail as unrecognized. calendar freebusy --cal accepts both.

Current (v0.47.1)

gog calendar events --cal primary
# unrecognized calendar name(s): primary      (exit 2)
gog calendar events --cal [email protected]
# unrecognized calendar name(s): [email protected]
gog calendar events primary                   # works

Suggested

Apply the same primary/@ short-circuit in the strict lookup, so --cal primary,[email protected] works as it does in freebusy.

Environment

gog v0.47.1 (main at 82e7fd6). Reproduced against a local fake of the Calendar API through GOG_GOOGLE_API_BASE_URL.

Dominant language
Go
Stars
8.5k
Forks
721
Avg merge
17h 48m
Merged PRs (30d)
52

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 openclaw/gogcli

All issues in openclaw/gogcli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.