fix(studio): stabilize OpenCLI preset and inspector UX - #47
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe workflow editor now preserves authored node labels, presents OpenCLI presets in a navigable catalog, adjusts viewport and inspector sizing behavior, and expands regression coverage for these changes. ChangesWorkflow editor changes
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant User
participant CommandPalette
participant OpenCLIPickerRow
participant addOpenCLIAdapter
User->>CommandPalette: choose an OpenCLI preset
CommandPalette->>OpenCLIPickerRow: render preset and availability
OpenCLIPickerRow->>addOpenCLIAdapter: add selected item
addOpenCLIAdapter-->>CommandPalette: update workflow
Possibly related PRs
Suggested reviewers: Poem
✨ Finishing Touches📝 Generate docstrings
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 |
|
✅ Health: 9.2 🚨 Change risk: 8.9/10 (high)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-27 17:00 UTC |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
What changed
Why
The workflow editor had four related usability failures: the OpenCLI capability catalog was hard to scan, long node configuration could not be reached, the same node appeared under different names across surfaces, and the inspector consumed most of the canvas on tablet/mobile widths.
Impact
Operators can browse the full OpenCLI catalog, edit long configurations, identify a node consistently, and retain usable canvas space on compact screens. No backend contract or runtime behavior changes.
Validation
npm run check:node-capabilities— 11/11 passednpm run check:workflow-regressions— 47/47 passednpx tsc --noEmit— passedgit diff --check origin/main...HEAD— passedThe local pre-push hook was bypassed only because unrelated untracked root
pnpm-workspace.yaml/pnpm-lock.yamlfiles made it mis-detect this frontend worktree as a root pnpm workspace; the relevant frontend checks above were run independently and passed.