Skip to content

Restore ThreadPanel KEY_STEP=16 source-pin (post-#55 E2E fix) - #56

Merged
Aztec03hub merged 1 commit into
mainfrom
fix/e2e-thread-keystep-pin
Jun 26, 2026
Merged

Restore ThreadPanel KEY_STEP=16 source-pin (post-#55 E2E fix)#56
Aztec03hub merged 1 commit into
mainfrom
fix/e2e-thread-keystep-pin

Conversation

@Aztec03hub

Copy link
Copy Markdown
Owner

Post-merge follow-up to #55.

The DRY resize-helper extraction in #55 moved the keyboard nudge step into the shared createResizablePanel default and dropped the local const KEY_STEP = 16 from ThreadPanel.svelte. That broke the source-level pin in web/e2e/scenarios/10-thread-panel.spec.ts ("ThreadPanel pins KEY_STEP = 16"), turning the post-merge E2E (Playwright scenarios) job red on main (web unit tests, build, lint, and Python suites all stayed green).

This re-declares KEY_STEP = 16 alongside its MIN_PANEL_WIDTH / MAX_PANEL_WIDTH / DEFAULT_PANEL_WIDTH / STORAGE_KEY siblings and passes it explicitly into the helper, so it is wired rather than dead. No behaviour change — the helper already defaulted keyStep to 16.

Verification: pnpm --dir web build green; pnpm --dir web test thread-panel spec green (21/21); all four pinned constants present in source.

🤖 Generated with Claude Code

…tion (#55 follow-up)

The DRY extraction in #55 moved the keyboard nudge step into the shared
createResizablePanel default and dropped the local `const KEY_STEP = 16`,
which broke the source-level pin in e2e/scenarios/10-thread-panel.spec.ts
("ThreadPanel pins KEY_STEP = 16") and turned post-merge CI red on the E2E
job (web unit tests + build + lint stayed green).

Re-declare KEY_STEP=16 alongside its MIN/MAX/DEFAULT/STORAGE_KEY siblings and
pass it explicitly into the helper so it is wired, not dead. No behaviour
change (the helper already defaulted keyStep to 16).
@Aztec03hub
Aztec03hub merged commit 4a6b292 into main Jun 26, 2026
8 checks passed
@Aztec03hub
Aztec03hub deleted the fix/e2e-thread-keystep-pin branch June 26, 2026 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant