Give the file-name template and its preview the whole card - #17
Merged
Conversation
The naming card was two half-width columns: the template box on the left, the rendered preview on the right. A path is the one thing on that page that genuinely needs the whole line — it is read for its tail as much as its head — and halving both meant neither had room. Template, preview, then the two shortcuts now run the card's full width in the order they are used: type a template, read what it produces, take a shortcut if it was not what you wanted. The preview sits in a recessed well rather than as loose text. It is the one thing in this card that is output rather than input, and without a surface of its own it read as a caption under the box instead of as the answer the box produces. The well is one tight line with its label inside it, and that is load-bearing rather than taste: the page has to fit the window's minimum height without scrolling, and a first attempt with the label on its own line above a two-line well pushed the bottom card off the end of the page — clipped mid-row, with no scrollbar to say so. A rendered path is one line in every realistic case, and the ellipsis and tooltip carry the ones that are not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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 freeto 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.
Advanced tab, file-name section.
The card was two half-width columns — template box left, rendered preview right. A path is the one thing on that page that genuinely needs the whole line (it is read for its tail as much as its head), and halving both meant neither had room.
Template, preview, then the two shortcut buttons now run the card's full width, in the order they are used: type a template, read what it produces, take a shortcut if it was not what you wanted.
The preview sits in a recessed well (
OffstreamWellBrush, a new token — darker than the card, lighter than the window). It is the one thing in this card that is output rather than input, and without a surface of its own it read as a caption under the box instead of as the answer the box produces.The well is one tight line, and that is load-bearing
A first attempt put the "Next file" label on its own line above a two-line well. That grew the card by roughly 80px, and since the page has to fit the window's 700px minimum without scrolling, the bottom card was pushed off the end — clipped mid-row, with no scrollbar to say so.
The label moved inside the well and the well is a single line with tight padding. A rendered path is one line in every realistic case; the ellipsis and tooltip carry the ones that are not.
AdvancedTemplatePreviewstays on the element holding the path itself, so automation still reads the path and not the label.(An intermediate version added a page-level
ScrollVieweras a floor against this class of failure. Removed at the author's direction — the page does not scroll.)Testing
App project builds clean,
dotnet format --verify-no-changesclean. Layout is visual and left to manual testing per standing instruction; no ViewModel or logic changed.🤖 Generated with Claude Code