#38 · Generate per-app API client snippets from wrangler.toml routes
Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
An MR completes this bounty when it is merged into main with Closes #38 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
Context
Developers don't know what endpoints each Worker exposes without reading source. Build a tool that ingests each app's wrangler.toml and source files and emits a one-page API reference with copy-paste TypeScript / curl examples.
Acceptance criteria
- [ ]
/apispage lists all 12 Workers with click-to-expand endpoint summary - [ ] For each endpoint: method, path, body schema (Zod), example response
- [ ] Snippets generated at build time from a registry, not scraped at runtime
- [ ] Updates trigger automatically when new endpoints land
Technical hints
- Existing pattern of registering routes in each app's
index.tsif (pathname === '/...' && method === ...)is parseable but ugly. Better: standardize aroutes.tsper app and have the developer-portal build read it. - OpenAPI 3.1 emitter would be overkill here — keep it simple
--- *Submit a merge request that says Closes #<this issue iid> in the description. On merge to main, the GitLab webhook will auto-award your bounty + the standard merge_pr (40 pts) to your scoreboard account. Email on commit must match your Authentik email.*
Relevant files
No relevant files linked yet.
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.