Repository navigation
feat(dashboard): show categories brought by tapped repositories in the sidebars - #4741
Conversation
…e sidebars The marketplace and console sidebars rendered a fixed IaaS / PaaS / NaaS list and dropped every other spec.dashboard.category. A repository tapped with cozypkg that brings its own category was reachable only through the full application list, and its installed applications had no console section. Follow groupByCategory instead, the order the marketplace page already uses, and keep Administration in the Admin portal. Assisted-by: LLM Signed-off-by: tym83 <[email protected]>
The sidebars now follow every category but Administration, so the note describes behaviour that no longer exists. Assisted-by: LLM Signed-off-by: tym83 <[email protected]>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe Marketplace and Console sidebars now show every category returned by ChangesSidebar category coverage
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to Tapped-repository categories now appear in the Marketplace and Console sidebars, while Administration remains in the Admin portal. No merge-blocking risk was identified. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to Custom categories do not change tenant selection or authorization. However, a specially named category can select an invalid icon and prevent the Marketplace interface from rendering for users sharing that catalog. Exploitation requires contributing an accepted application definition; no backend privilege escalation was identified. Retained concerns
Security review detailsSecurity Blast Radius
Security Findings and Attack Paths
Trust Boundaries and Controls
Resilience and Maintainability Implications
Hardening Proposals
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 4 functions across 2 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Aleksei Sviridkin (lexfrei)
left a comment
There was a problem hiding this comment.
Timur Tukaev (@tym83) LGTM. On a trial merge with current main, sidebar-sections.test.tsx passes, and both new cases fail when sidebar-sections.tsx is put back to main. So the tests pin the change. CATEGORY_ICON[category] ?? LayoutGrid covers the unknown-category icon, and the removed note in docs/agents/contributing.md described exactly the behaviour this replaces.
Non-blocking: this also changes a stock install, which the PR body does not mention. external-dns-rd ships category: Networking without module: true, so a default cluster gets a new "Networking" section in both sidebars, next to "NaaS". If that is intended, fine. If not, moving ExternalDNS to NaaS would keep one networking section.
What this PR does
The marketplace and console sidebars render a fixed category list,
["IaaS", "PaaS", "NaaS"], and drop every otherspec.dashboard.category. A repository tapped withcozypkgthat brings its own category is reachable only at the bottom of the full application list, and its installed applications get no console section at all.Both sidebars now follow
groupByCategory, the order the marketplace page already uses: IaaS, PaaS, NaaS first, then any other category alphabetically.Administrationstays in the Admin portal, as before. Unknown categories get the generic grid icon.The note in
docs/agents/contributing.mdthat described the hardcoded list is removed, since it no longer holds.Tests: two new cases in
sidebar-sections.test.tsx(a tappedPaleocomputingcategory appears after the built-in ones in both sidebars,Administrationstays out). Both fail on the previous code. The console suite (448 tests),pnpm typecheckandeslinton the changed files pass.Screenshots
Same cluster and tenant, a repository tapped that brings the
Paleocomputingcategory.Before, marketplace: the category is only reachable at the bottom of the full list.
After, marketplace: the category gets its own filter.
Before, console: no section for the tapped applications.
After, console: installed applications of that category get their own section.
Downstream repositories
Walked the trigger map against the diff: it touches only the console sidebar code and a note in
docs/agents/contributing.md. No package, values schema, CRD, installer value orApplicationDefinitionfield changes. The website page onApplicationDefinitiondoes not restrictspec.dashboard.categoryvalues, andexternal-apps-exampleusesPaaS, which keeps working as before.Release note
Summary by CodeRabbit