Clearer error for a stale or trashed page_id on update

Open
#17 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, cli

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.

Description

bug

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.)

Dominant language
Go
Stars
2
Forks
0
Avg merge
2h 5m
Merged PRs (30d)
50

Contributor guide

Open the 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 mozilla/markfluence

All issues in mozilla/markfluence

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.