api: remove dead UI stubs and stale issue references in api_stubs.go
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Start in internal/api/api_stubs.go, where the two dead stubs (GET /api/v2/backfills and POST /api/v2/connections/defaults) and the comment that cites issues #26 to #32 live. Check the claim that no UI bundle calls them by searching the generated client hooks and src/, then find the stub tests and the website/content/concepts/ui-compatibility.md page. Done means the dead stubs and their tests are removed or kept with an accurate comment, and the stub comments point to open issues or that doc instead of closed ones.
Written by the indexing model from the issue text.
Description
Cleanup in the UI stubs:
GET /api/v2/backfillsandPOST /api/v2/connections/defaults(internal/api/api_stubs.go) are called by neither the 3.2.1 nor the 3.3.2 bundle (no use in the generated client hooks or insrc/). The comment on the connections stub says the UI POSTs there when the Connections area opens; neither bundle does.- The file comment says real implementations are "tracked per endpoint (GitHub issues #26 to #32)", but #26, #27, #28, #29, #30 and #32 were closed as not planned on 2026-07-28.
Acceptance
- Remove the two dead stubs and their tests, or keep them with a comment that is true.
- Point the stub comments at open issues or at
website/content/concepts/ui-compatibility.mdinstead of closed issues.
Found while auditing the 3.2.1 to 3.3.2 UI bump (#835, #1676).
Generated by Claude Code
- Dominant language
- Go
- Stars
- 46
- Forks
- 1
- Avg merge
- 13h 9m
- Merged PRs (30d)
- 686
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from dexadata/dexaflow
-
area/docs documentation priority/p3
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/ci enhancement priority/p3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 3-5 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in dexadata/dexaflow
Similar issues
-
feat(gmail): make gmail get --format raw text output the exact message, like drafts get --format rawOpenclawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openclaw/gogcli#1276 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hiero-ledger/hiero-sdk-go#1886 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudevents/sdk-go#1346 ·