Skip to content

feat(composer): drop the build history so the composer sits centred - #206

Merged
PouyanJay merged 1 commit into
mainfrom
fix/composer-center-only
Aug 2, 2026
Merged

feat(composer): drop the build history so the composer sits centred#206
PouyanJay merged 1 commit into
mainfrom
fix/composer-center-only

Conversation

@PouyanJay

Copy link
Copy Markdown
Owner

Removes the recent-builds table from the composer, which also fixes the centring.

Why it wasn't centring

safe center was working correctly the whole time. The build history made the column taller than the viewport, so it fell back to top alignment, which is exactly what safe is for. Remove the table and the composer is short enough to sit in the middle of the page. No CSS change was needed.

What went with it

RecentBuildsTable, its stylesheet and its test are deleted rather than left unused. The test harness's router wrapper went too, since that table's links were the only thing in the composer that navigated.

The runs prop stays, read only to tell a first-time visitor from a returning one, so the first-run explainer still appears once and only once.

One consequence worth knowing

This was the only surface in the app where a cancelled or failed build was visible. Home lists running builds; the library lists finished courses. A build that was cancelled now appears nowhere.

That's a deliberate trade for a cleaner entry surface rather than an oversight, and it's the thing to revisit if failed builds ever need somewhere to live.

1461 tests green · typecheck, lint, build clean.

The recent-builds table is gone from the composer, and with it the reason
the column was not centring. `safe center` was working correctly all
along: the table made the content taller than the viewport, so it fell
back to top alignment exactly as designed. Remove the table and the
composer is short enough to sit in the middle of the page.

RecentBuildsTable, its stylesheet and its test are deleted rather than
left unused. The router wrapper its links needed went with it, since it
was the only thing in the composer that navigated.

Worth stating plainly: this was the ONLY surface in the app where a
cancelled or failed build was visible. Home lists running builds and the
library lists finished courses, so a build that was cancelled now shows
up nowhere. That is a deliberate trade for the cleaner entry surface, not
an oversight, and it is the thing to revisit if failed builds ever need
somewhere to live.

The `runs` prop stays, read only to tell a first-time visitor from a
returning one so the explainer still shows once and only once.

1461 tests green. Typecheck, lint, build clean.
@PouyanJay
PouyanJay merged commit 8ae4622 into main Aug 2, 2026
6 checks passed
@PouyanJay
PouyanJay deleted the fix/composer-center-only branch August 2, 2026 18:09
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