Repository navigation
feat(ui): createControlRail, the header's controls as a vertical rail - #45
Merged
Merged
Conversation
The left control rail in the playground was ~120 lines of app code, so hosts such as bloxwap.pro could only get the top header bar. - createControlRail (@bloxwap/chart/ui): timeframe and chart-type menus, Indicators, Auto / % / Log toggles, and top / bottom host slots in a 52px rail beside the drawing toolbar. Same options, datafeed rules and handle as createChartHeader; menus open right with hover intent - The header's keyboard dropdown and radio entries move to a shared menu-controls module, so both menus behave identically - Rail styles (slots, scale toggles, footer) ship in TOOLBAR_CSS - Playground builds its rail with createControlRail - Docs: control rail section in the header guide, exports, READMEs, llms.txt Co-Authored-By: Claude Opus 5.5 <[email protected]>
Merged
joeblau
added a commit
that referenced
this pull request
Sep 30, 2026
- Set @bloxwap/chart (and the workspace apps) to 0.3.0 for the control rail release (#45) - Docs, README, llms.txt, OpenAPI and the site's structured data name 0.3.0; llms.txt lists the vertical control rail in the UI layer Co-authored-by: Claude Opus 5.5 <[email protected]>
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
1 participant
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.
Why
bloxwap.pro shows a top header bar, but the playground has a left control rail. That rail was ~120 lines of playground-only code, so the library only offered
createChartHeaderand apps could not use the rail.What
createControlRailin@bloxwap/chart/ui: the header's controls stacked in a 52px rail beside the drawing toolbar.slots.top(scrolls with the controls) andslots.bottom(pinned footer).createChartHeader.slotsare exposed as live containers, so hosts can move buttons between the rail and a header.menu-controls.ts, so the header and the rail share one implementation. The header's behavior is unchanged.TOOLBAR_CSS, so the playground's rail-only CSS is gone.createControlRail. One small change: the right-edge panel button now sits below Log, in the top slot, instead of after Indicators.Testing
node scripts/check-coverage.mjs: all 1869 tests pass, with 100% line, branch and function coverage (new filescontrol-rail.jsandmenu-controls.jsincluded).npm run docs:checkpasses.Follow-up
Release 0.3.0, then switch
workers/pro/src/components/chart/bloxwap-chart.tsxfromcreateChartHeadertocreateControlRail.🤖 Generated with Claude Code