cameleer/cameleer-saas
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

TopBar shows server-specific controls on SaaS pages #53

New Issue
Closed
opened 2026-04-10 09:56:03 +02:00 by claude · 1 comment
claude commented 2026-04-10 09:56:03 +02:00
Owner
Copy Link

Problem

The TopBar from @cameleer/design-system includes server-specific controls (OK/Warn/Error/Running filter buttons, time range selector) that don't apply to SaaS vendor/tenant portal pages.

Expected

Either:

  • A) TopBar accepts a prop to hide server-specific controls
  • B) SaaS uses a simpler header without those controls
  • C) Design system provides a "platform" variant of the TopBar

Current behavior

Filter buttons and time range tabs are always visible on all SaaS pages (vendor console and tenant portal). They don't do anything since there are no server exchanges to filter.

Scope

Requires design-system change (new prop or variant) + SaaS frontend update.

## Problem The TopBar from `@cameleer/design-system` includes server-specific controls (OK/Warn/Error/Running filter buttons, time range selector) that don't apply to SaaS vendor/tenant portal pages. ## Expected Either: - A) TopBar accepts a prop to hide server-specific controls - B) SaaS uses a simpler header without those controls - C) Design system provides a "platform" variant of the TopBar ## Current behavior Filter buttons and time range tabs are always visible on all SaaS pages (vendor console and tenant portal). They don't do anything since there are no server exchanges to filter. ## Scope Requires design-system change (new prop or variant) + SaaS frontend update.
claude commented 2026-04-10 17:06:43 +02:00
Author
Owner
Copy Link

Fixed by decomposing TopBar into a composable shell with a children slot.

design-system (v0.1.40):

  • TopBar now accepts children for the center area — no longer hardcodes server-specific controls
  • Extracted SearchTrigger and AutoRefreshToggle as standalone components
  • Removed dependency on useGlobalFilters and useCommandPalette from TopBar

cameleer3-server (2863cee):

  • LayoutShell composes TopBar children: SearchTrigger, ButtonGroup (status filters), TimeRangeDropdown, AutoRefreshToggle
  • Visually identical to before

cameleer-saas (269c679):

  • Removed GlobalFilterProvider and CommandPaletteProvider wrappers from main.tsx
  • TopBar now renders only breadcrumb + theme toggle + user menu on SaaS pages
Fixed by decomposing TopBar into a composable shell with a `children` slot. **design-system** (`v0.1.40`): - TopBar now accepts `children` for the center area — no longer hardcodes server-specific controls - Extracted `SearchTrigger` and `AutoRefreshToggle` as standalone components - Removed dependency on `useGlobalFilters` and `useCommandPalette` from TopBar **cameleer3-server** (`2863cee`): - LayoutShell composes TopBar children: SearchTrigger, ButtonGroup (status filters), TimeRangeDropdown, AutoRefreshToggle - Visually identical to before **cameleer-saas** (`269c679`): - Removed `GlobalFilterProvider` and `CommandPaletteProvider` wrappers from main.tsx - TopBar now renders only breadcrumb + theme toggle + user menu on SaaS pages
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
Identity, authentication, OIDC, RBAC
 billing
Billing, metering, and Stripe integration
 day-1
Required for initial launch
 epic
Top-level epic grouping related issues
 future
Planned for future release
 infra
Infrastructure, GitOps, K8s orchestration
 licensing
License module and feature gating
 networking
Network isolation, VPN, tenant separation
 observability
Observability integration (cameleer3-server)
 ops
Platform operations and self-monitoring
 phase-1
Phase 1: Foundation + Auth
 phase-2
Phase 2: Tenants + Licensing
 phase-3
Phase 3: Runtime Orchestration + Environments
 phase-4
Phase 4: Observability Pipeline + Inbound Routing
 phase-5
Phase 5: K8s Operational Layer
 phase-6
Phase 6: Billing + Metering
 phase-7
Phase 7: Billing + Metering
 phase-8
Phase 8: Security Hardening + Self-Monitoring
 phase-9
Phase 9: Frontend (React Shell)
 platform
SaaS management platform
 runtime
Camel application runtime
 secrets
Secrets management and vault integration
 security
Security, compliance, SOC 2, audit
 task
Implementation task within a phase
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-saas#53
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?