Repository navigation
feat(llc): Kanban boards UI wired to the boards API (list/create/move) (#12213) - #12254
Merged
Merged
Conversation
Contributor
✅ SSOT Configuration Compliance: Passing🎉 No hardcoded values detected that have SSOT config equivalents! |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thinking Path
Audit-first (issue premise was stale). The LLC Kanban board UI already exists and is reachable:
BoardsView(list),KanbanBoardView(drag-and-dropPOST /move, WIP limits),SprintBoardView, all routed under/llc/companies/:companyId/...with anav.llcBoardssidebar entry. So theGET /boards,GET /{id},GET /{id}/items,POST /{id}/moveendpoints were already consumed.The one genuine gap: the board create endpoints (
POST /api/llc/boards/kanban,POST /api/llc/boards/sprint) had zero frontend callers — a fresh company's empty board list was a dead end (nothing ever creates a board). This wires the create path rather than duplicating the existing views.What Changed
useKanbanBoardsApi(autobot-frontend/src/composables/llc/useKanbanBoardsApi.ts) centralising list / create-kanban / create-sprint / move againstllc/api/boards.py.BoardsView.vue— adds a "New Kanban Board" affordance (header button + empty-state CTA) that opens a project picker (GET /api/llc/companies/{id}/projects), callscreateKanbanBoard(get-or-create), and navigates to the new board. Reuses the existingBaseModal+ design-token styling; no new design language, no hardcoded strings.llc.boards.{newKanban,createTitle,project,selectProject,loadingProjects,noProjects,creating,create}to all 11 locales (translated de/es/fr/pt; English fallback for the rest, matching the existing partial-coverage pattern in the boards block).useKanbanBoardsApi.test.ts(6 tests) asserting each call hits the right endpoint + payload and parses responses.Verification
npx vitest run src/composables/llc/__tests__/useKanbanBoardsApi.test.ts→ 6 passed.npx vue-tsc --noEmit -p tsconfig.app.json→ no errors in touched files.npx eslint <touched files>→ clean (exit 0).Model Used
claude-opus-4-8
Closes #12213