Repository navigation
Reorganise the Switches page around the switch list - #897
Merged
Merged
Conversation
enaboapps
force-pushed
the
886-forms
branch
from
September 25, 2026 10:56
43a3ebd to
1e11013
Compare
enaboapps
force-pushed
the
887-switches-page
branch
from
September 25, 2026 10:56
6ef8559 to
ffd742d
Compare
enaboapps
force-pushed
the
886-forms
branch
from
September 25, 2026 11:03
1e11013 to
082ec0a
Compare
enaboapps
force-pushed
the
887-switches-page
branch
from
September 25, 2026 11:03
ffd742d to
cf22bc7
Compare
The section leads with its save status and Add switch in a toolbar, then the list; the practice tool follows as a quiet card with its source and start button on one line. Add switch keeps one fixed position in every state so focus survives switch data loading. Each row leads with its key badge, visually only, keeping the Edit then Remove order. The empty state tells people what to press, and buttons in setting groups and editor fields keep their natural width. Closes #887 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
enaboapps
marked this pull request as ready for review
September 25, 2026 11:49
enaboapps
force-pushed
the
886-forms
branch
from
September 25, 2026 11:50
082ec0a to
19db7ff
Compare
enaboapps
force-pushed
the
887-switches-page
branch
from
September 25, 2026 11:50
cf22bc7 to
9789273
Compare
enaboapps
marked this pull request as draft
September 25, 2026 11:50
enaboapps
marked this pull request as ready for review
September 25, 2026 14:44
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
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.
Closes #887. Stacked on #896, tracked in #891.
What changed
Validation
On this head:
npm run lintpassednpm testpassed: 238 Vitest tests and 5 Node testsnpm run buildpassedcargo fmt --check,cargo clippy --all-targets -D warningsandcargo testpassed (566 tests, 1 ignored). No Rust changes in this stack.Review follow-up
An independent review of this layer's head raised these points, now addressed:
🤖 Generated with Claude Code
Rebase validation (2026-09-25)
Rebased onto current
main(7fb8fce, including #881) in stack order.git range-diffshows every commit in this PR is patch-equivalent to its previous head, and the intended parent remains its PR base. On the final stack tip (40c75cc), Node 24.19.0 lint, tests and build passed; Rust 1.97.1 format check, Clippy and tests passed. An independent review of the updated PR heads found no actionable findings. CI is rerunning on each new head.