Skip to content

v0.4.1 — a highlight could become uncommentable

Choose a tag to compare

@skurekjakub skurekjakub released this 31 Aug 12:44
· 17 commits to main since this release

The bug

0.4.0 moved the comment box into a popover anchored to the selection, and in the same change removed the tray's own + Add row — making the popover the only way to attach a comment.

The popover needs a rectangle to position against, and not every selection yields one. Wherever the anchor came back empty, the highlight was dropped silently with nothing left to click. Preview never showed it, because a clean mouse drag always produces a rectangle.

The fix

The tray takes the pending selection again. The popover is the quick path; the tray row is the one that is always there. Both are live at once and either pins the passage, so the feature no longer depends on a measurement succeeding.

Also fixed:

  • The diff pane listens for selections in its empty branch too — that is what an unchanged file renders through.
  • npm run bump leaves the tree formatted. Its prettier step had never run: a deprecated shell invocation, then npx.cmd, which fails on Windows with EINVAL after writing — so a bump produced a correct version and a failing format:check.

187 tests. Reinstall the .mcpb below.