Clearer error for a stale or trashed page_id on update
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 49
Description
When a markdown file's frontmatter page_id no longer exists in Confluence, update fails with a raw HTTP 404 (from GetPage, or from the v1 attachment API when the page is merely trashed — v2 still returns trashed pages while the v1 attachment endpoint 404s).
Detect the missing/trashed page up front in the update flow and emit a clear message, e.g. "page <id> from frontmatter no longer exists in Confluence; remove the page_id to recreate it with create, or fix the id" — instead of a bare 404. (From the old todo.md.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the update flow and trace the GetPage call, then inspect the v1 attachment API behavior for trashed pages alongside the v2 response. Reproduce both missing and trashed page_id cases, and confirm update emits the requested clear message instead of a raw 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100