Repository navigation
chore: v0.0.3, the release where the window stops deciding for you - #91
Merged
Merged
Conversation
Six commits since v0.0.2, and four of them are about the same complaint: the window decided how much of anything you were allowed to read, and there was no way to argue with it. **The panes are divided where you drag them.** A 230px sidebar, a 6:4 graph against the detail pane and a 280px file list were three guesses about a window nobody had seen. Every divider between them is draggable now, double-clicking one puts it back, and where they are left is written to `state.toml` with the window's own geometry. Two are pixels and one is a fraction, because a branch name does not get longer when the window does and the graph and the commit under it are two halves of one view. **Text nobody chose the length of scrolls instead of being cut off.** A commit message of four paragraphs was drawn at whatever height it asked for and then clipped — no scrollbar, no wheel, no way to read the end of it. Git's stderr did the same in a failed pane, and in a toast it grew *upwards*, carrying the summary and Copy details off the top of the window on exactly the failures worth reporting. **A native menu bar, on macOS.** What was up there was winit's fallback: one menu, naming the executable rather than the application, with no File and no Edit — so no Copy or Paste in a menu, and no way to discover that Cmd+O opens a repository except by already knowing. It is built from the command palette's own table, so an item's title, action and shortcut cannot disagree with the palette's, and the shortcut it shows is the one you remapped it to. Windows and Linux keep no menu bar, which ADR-0009 says out loud rather than leaving to be found. **Empty states carry the action they describe.** A clean working directory offers the commit it matches instead of telling you to go and find it; a file filter that matches nothing offers to clear itself.
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.
Six commits since v0.0.2, four of them about the same complaint: the window decided how much of anything you were allowed to read, and there was no way to argue with it.
state.tomlThis PR is the version bump alone:
[workspace.package]and the three path dependencies, plus the lockfile. The tag has to match the manifest or the release workflow's first job fails before anything compiles —docs/RELEASING.mdexplains why.Tagging
v0.0.3after this merges publishes the archives.