mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-08-03 21:34:40 +00:00
49497f5076
* feat(web-shell): color-code each split pane by workspace On a narrow split (split-screen / mobile), it was hard to tell which workspace each pane belonged to: a pane's header showed only its session name, and the sole workspace signal — the composer chip at the bottom — collapsed to a bare folder icon that looked identical for every workspace, so the workspace was discoverable only by hovering each one. Surface the workspace where you actually scan — the pane header — and give each workspace a stable accent color so panes read apart at a glance and same-workspace panes read as a group: - Add a colored workspace tag (dot + basename) at the start of each pane header on a multi-workspace daemon, and colorize the header divider with the same accent. The dot never shrinks, so panes stay distinguishable even when the name and session title ellipsize. - Derive a stable per-workspace color from the workspace's position in the daemon's advertised workspaces[], reusing the sidebar session-group palette so the two surfaces speak the same color language. Extracted into a shared workspaceAccent.module.css. - Tint the composer workspace chip with the same accent (folder + faint background) so it stays distinguishable even in its icon-only compact state, instead of a generic folder. Single-workspace daemons are unchanged: no tag, and the header divider falls back to the neutral border. * refactor(web-shell): address review on split-pane workspace accent - Rename workspaceAccent.module.css -> WorkspaceAccent.module.css to match the PascalCase convention used by every other component .module.css; update both import sites. - Hoist the four raw-hex accent colors (red/orange/yellow/green) into shared --accent-* theme tokens in App.module.css, and point the workspace accent module, the sidebar group dots, and the overview badges at them. The palette now has a single source of truth and can't drift between the four surfaces (values are unchanged, so rendering is identical). - Add a compile-time exhaustiveness guard so adding a DaemonSessionGroupPresetColor without extending WORKSPACE_ACCENT_COLORS (and its CSS class) fails the build instead of silently dropping that accent. - Give the pane-header workspace tag role="img" so its "Workspace: <name>" aria-label is reliably announced; aria-label on a bare span (generic role) is not. * refactor(web-shell): address follow-up review on workspace accent - Hoist the four --accent-* tokens out of both theme blocks into the theme-independent .app scope, so they are declared once (the values do not vary by theme) — a genuine single declaration rather than two kept in sync. - Add a dev-only runtime check that every accent color has a matching class in WorkspaceAccent.module.css, closing the gap the compile-time guard cannot cover: CSS modules are typed Record<string, string>, so a renamed/removed class would otherwise silently drop that color's accent. - Rename the "same workspace same color" test to describe what it actually asserts (a stable color per cwd, and distinct colors across workspaces). * refactor(web-shell): address second follow-up review on workspace accent - WorkspaceIndicator tests: assert on imported CSS-module class names instead of string literals, so a CSS-module naming change can't silently make the substring checks vacuous; add an expanded-mode (non-compact) accent test so a refactor that gated the accent on `compact` would be caught. - workspaceColor.ts: run the CSS-class contract check unconditionally — throw in dev, but console.error in production — so a missing class in a prod build is at least diagnosable instead of a silent accent drop. - WorkspaceAccent.module.css: correct the docstring to state exactly which tokens come from where — red/orange/yellow/green from --accent-* in App.module.css, blue/purple deliberately reusing the --agent-* brand tokens. --------- Co-authored-by: wenshao <wenshao@example.com>
38 lines
1.4 KiB
CSS
38 lines
1.4 KiB
CSS
/**
|
|
* Per-workspace accent palette, mirrored from the sidebar session-group colors
|
|
* so the two surfaces speak the same color language. Each class only sets the
|
|
* `--ws-accent` custom property, which the consuming component reads to tint a
|
|
* dot, divider, or chip. Shared between the split-view pane header (ChatPane)
|
|
* and the composer workspace chip (WorkspaceIndicator) so a workspace looks the
|
|
* same in both places.
|
|
*
|
|
* Values come from shared theme tokens in App.module.css, kept in lockstep with
|
|
* the sidebar `.groupColor*` dots and overview `.color*` badges: red/orange/
|
|
* yellow/green resolve the theme-independent `--accent-red/orange/yellow/green`
|
|
* tokens, while blue/purple deliberately reuse the app's brand tokens
|
|
* `--agent-blue-500` / `--agent-purple-600` (which are theme-specific) — so a
|
|
* "blue" or "purple" workspace tracks the brand palette and shifts with it by
|
|
* design, matching how the sidebar and overview render those two.
|
|
*
|
|
* Class names deliberately match the `DaemonSessionGroupPresetColor` values so
|
|
* a consumer can select one with `accentStyles[color]`.
|
|
*/
|
|
|
|
.red {
|
|
--ws-accent: var(--accent-red);
|
|
}
|
|
.orange {
|
|
--ws-accent: var(--accent-orange);
|
|
}
|
|
.yellow {
|
|
--ws-accent: var(--accent-yellow);
|
|
}
|
|
.green {
|
|
--ws-accent: var(--accent-green);
|
|
}
|
|
.blue {
|
|
--ws-accent: var(--agent-blue-500);
|
|
}
|
|
.purple {
|
|
--ws-accent: var(--agent-purple-600);
|
|
}
|