christian/commitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Gitea read client behind an injected fetch #1

New Issue
Closed
opened 2026-07-08 15:15:07 +00:00 by christian · 1 comment
christian commented 2026-07-08 15:15:07 +00:00
Owner
Copy Link

Typed client in @commitea/core that round-trips one real object: fetch a single issue with its labels, milestone, and assignee, normalized to a GiteaIssue. Network is an injected fetch-shaped fn so it unit-tests with a stub. Token/base-URL from config, not hardcoded.

Acceptance: given canned JSON, returns a typed issue.

Tap-root — P1, P4-3, and all real-data work sink into this. Grab first.

Typed client in `@commitea/core` that round-trips one real object: fetch a single issue with its labels, milestone, and assignee, normalized to a `GiteaIssue`. Network is an injected fetch-shaped fn so it unit-tests with a stub. Token/base-URL from config, not hardcoded. **Acceptance:** given canned JSON, returns a typed issue. **Tap-root** — P1, P4-3, and all real-data work sink into this. Grab first.
christian added this to the P1 — Sync + data model milestone 2026-07-08 15:15:07 +00:00
christian added the
est
2d
p
1
 labels 2026-07-08 15:15:07 +00:00
christian added a new dependency 2026-07-08 15:15:41 +00:00
#2 ChangeSource interface + polling source
christian added a new dependency 2026-07-08 15:15:41 +00:00
#3 SQLite cache bootstrap + single-issue mirror upsert
christian added a new dependency 2026-07-08 15:15:42 +00:00
#6 pm-state repo reader
christian added a new dependency 2026-07-08 15:15:45 +00:00
#24 apply_changes unified mutation tool
christian commented 2026-07-08 20:45:50 +00:00
Author
Owner
Copy Link

Done in PR #35 (d6f531e). Gitea read client landed in @commitea/core (injected fetch, normalized GiteaIssue, GiteaApiError), unit-tested + verified against live #9.

Done in PR #35 (d6f531e). Gitea read client landed in @commitea/core (injected fetch, normalized GiteaIssue, GiteaApiError), unit-tested + verified against live #9.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deadline
hard
CommiTea: milestone has a hard deadline
est
1d
CommiTea estimate: 1 ideal-day(s)
est
2d
CommiTea estimate: 2 ideal-day(s)
est
3d
CommiTea estimate: 3 ideal-day(s)
est
5d
CommiTea estimate: 5 ideal-day(s)
est
8d
CommiTea estimate: 8 ideal-day(s)
p
1
CommiTea priority 1 (1 = most urgent)
p
2
CommiTea priority 2 (1 = most urgent)
p
3
CommiTea priority 3 (1 = most urgent)
p
4
CommiTea priority 4 (1 = most urgent)
No Label
est
2d
p
1
Milestone
No items
No Milestone P1 — Sync + data model
Projects
Clear projects
No project
Assignees
Clear assignees
christian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#2 ChangeSource interface + polling source
christian/commitea
#3 SQLite cache bootstrap + single-issue mirror upsert
christian/commitea
#6 pm-state repo reader
christian/commitea
#24 apply_changes unified mutation tool
christian/commitea
Reference: christian/commitea#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?