Repository navigation
POST /milestones/:id/allocate and /bounties/:id/approve|reject are documented in Swagger as working operations #613
Description
Problem
While these three routes are stubs (see the #253 regression), Swagger presents them with summaries such as "Approve a claimed bounty" and standard success responses. API consumers building against /api/docs have no hint that nothing happens.
Suggested fix
Mark them @ApiOperation({ deprecated: true, description: 'Not implemented' }) or exclude them until they're implemented.
Related: #253
Activity
tresjo81 commentedon Oct 13, 2026
Hi team! I'd like to take this on. I can mark these stub operations with
@ApiOperation({ deprecated: true, description: 'Not implemented' })(or omit/document appropriately per guidelines) so Swagger accurately reflects the current status of these endpoints. Could you please assign this to me?docs(api): mark the stub allocate/approve/reject routes deprecated in…
docs(swagger): mark stub endpoints as deprecated and not implemented (M…
Ranjeet2063 commentedon Oct 26, 2026
Hello maintainers,
Happy to work on this in backend. I have a clean approach to address POST /milestones/ and will verify the implementation against existing test suites. Please feel free to assign it to me.
Cheers,