Fix incorrectly generated Swagger docs for /labelmaker/asset/{id} route

[adarshp]

What type of PR is this?

• bug
• documentation

What this PR does / why we need it:

This PR fixes incorrectly generated swagger docs by fixing the relevant comment line in v1_ctrl_labelmaker.go to match the route in routes.go:

homebox/backend/app/api/routes.go

Line 172 in a379e7c

r.Get("/labelmaker/asset/{id}", chain.ToHandlerFunc(v1Ctrl.HandleGetAssetLabel(), userMW...))

.

Also see #1077 .

Which issue(s) this PR fixes:

Addresses #1077 .

Testing

I have not tested the Swagger documentation autogeneration, but I think this change is unlikely to break it.

Summary by CodeRabbit

• Bug Fixes
  • Corrected the API endpoint path for Asset label retrieval from /v1/labelmaker/assets/{id} to /v1/labelmaker/asset/{id}.

[coderabbitai]

Walkthrough

The Asset label endpoint route annotation was updated from the plural form /v1/labelmaker/assets/{id} to the singular form /v1/labelmaker/asset/{id}. No function logic, parameters, or return values were modified.

Changes

Cohort / File(s)	Summary
API Route Path Update backend/app/api/handlers/v1/v1_ctrl_labelmaker.go	Changed router annotation for GET asset label endpoint from plural to singular form: /v1/labelmaker/assets/{id} → /v1/labelmaker/asset/{id}

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Security & compatibility notes:

• ⚠️ This is a breaking change for any API clients currently using the /v1/labelmaker/assets/{id} endpoint—they will receive HTTP 404 responses
• Verify that proper API deprecation strategy or redirects are in place for backward compatibility
• Ensure consistency across other labelmaker endpoints (confirm all use singular vs. plural form)
• Consider publishing a migration guide if external consumers depend on this endpoint

Poem

🛣️ A path from plural to singular flows,
/assets becomes /asset as the API grows—
One word simpler, one route refined,
Small change in form, but breaking in kind. 🔄

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: fixing incorrectly generated Swagger documentation for a specific API route.
Description check	✅ Passed	The description includes all required sections (PR type, what it does, which issues it fixes) with sufficient detail about the routing fix and relevant context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a379e7c and e7f1b6e.

📒 Files selected for processing (1)

• backend/app/api/handlers/v1/v1_ctrl_labelmaker.go (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (18)

• GitHub Check: End-to-End Playwright Tests / E2E Playwright Testing 1/4
• GitHub Check: End-to-End Playwright Tests / E2E Playwright Testing 3/4
• GitHub Check: End-to-End Playwright Tests / E2E Playwright Testing 4/4
• GitHub Check: End-to-End Playwright Tests / E2E Playwright Testing 2/4
• GitHub Check: Frontend Tests / Integration Tests PGSQL 17
• GitHub Check: Frontend Tests / Integration Tests PGSQL 16
• GitHub Check: Frontend Tests / Integration Tests PGSQL 15
• GitHub Check: Backend Server Tests / Go
• GitHub Check: Frontend Tests / Integration Tests
• GitHub Check: build (linux/arm/v7)
• GitHub Check: build (linux/amd64)
• GitHub Check: build (linux/arm64)
• GitHub Check: build (linux/arm/v7)
• GitHub Check: build (linux/arm64)
• GitHub Check: build (linux/amd64)
• GitHub Check: build (linux/arm64)
• GitHub Check: build (linux/amd64)
• GitHub Check: build (linux/arm/v7)

🔇 Additional comments (1)

backend/app/api/handlers/v1/v1_ctrl_labelmaker.go (1)

106-106: Swagger documentation route corrected to singular form.

The Swagger annotation has been updated to match the actual route definition in routes.go. The route correctly uses the singular form /v1/labelmaker/asset/{id}, and no references to the old plural route remain in the codebase. This is a documentation-only change with no impact on runtime behavior.

Security considerations:

• Ensure any API client SDKs or external documentation referencing this endpoint are updated to use the singular route path to prevent endpoint discovery failures.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining why this PR is needed, why this solution was chosen, and what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}