Skip to content

Diffwright 0.17.0

Latest

Choose a tag to compare

@Jpi-net Jpi-net released this 26 Oct 09:03

Features

  • Code navigation without leaving the diff: a click on a function, class or variable opens its
    definition in a before / after preview (with the right candidate when a name is ambiguous), its
    usages inside and outside the PR, an outline of the changed symbols, “Explain this symbol” on
    demand, a trail with back navigation, read-only access to files outside the PR, a cautious mode
    that avoids uncertain jumps, and a beta “Fast mode” (a local git clone managed by Diffwright, off
    by default).
  • Accessibility: linear text diff, contextual help and a dedicated settings page: an accessible
    diff view reads each line with its state (added, removed, unchanged) and its threads, a contextual
    help explains the keys that work where the focus is, an Accessibility page in Settings gathers
    text size and spacing, contrast, transparency, animations, focus and screen reader options, and a
    shortcut moves between screen regions.
  • Per-hunk review, entirely from the keyboard: each changed block can be marked seen or to
    review (a gauge tracks progress), the keyboard chains to the next unseen block, the previous one,
    marking the file and then the next file to review, and everything stays on your machine with
    nothing ticked or sent to the platform.
  • Line comment: add it to your review or publish it right away: confirming a comment (or a code
    suggestion, or test feedback) now keeps it in your review without publishing anything, and
    “Publish now” sends that single comment, with the buttons showing their key.
  • Azure DevOps: see what each iteration changed: a files-by-iteration grid (with one row per
    reviewer and their last seen iteration, inferred), files unchanged since your review folded away,
    only the new or touched blocks highlighted in the diff, and a “Fixed?” badge on a thread whose
    code changed after a push, all read-only.
  • Review: “Before approving” above the vote: a card of reminders, never a verdict, sums up what
    is left to look at (open threads, PR checks, symbols still used elsewhere, changed sources with no
    test touched, risks, files to review), each line taking you to the relevant place without writing
    anything.
  • Clearer vote and “Approve again”: “Approve” becomes the main button, the other verdicts are
    quiet icons, and if you voted before a new push the card says so and offers to approve again or
    see what changed, sending nothing without your click.
  • The live build in the Pull Request: a “Build” card shows the stages, the running task, elapsed
    time, an end estimate when history is reliable and whether the build blocks the merge, a line
    under the PR status sums it up on every tab, and the card updates itself while the build runs.
  • Failing tests: list, markers in the diff, watching and “Why does it break?”: the failing tests
    of a build are grouped by suite with expected and actual values, show up in the diff (margin mark,
    message at the end of the line, jumping from one failure to the next), can be watched locally from
    one build to the next, and one click asks the AI assistant for a likely cause without sending
    anything else or publishing.
  • Offline reading: your open PRs stay readable without a network: a banner reports the outage,
    the latest open PRs stay readable from this computer, write actions are disabled with the reason,
    a typed comment stays a local draft, and Settings › Local data lets you turn the feature off or
    forget the kept PRs.
  • My statistics: your review pace, calculated on your computer: a personal dashboard shows your
    reviewed PRs, comments, votes, turnaround and reading time over 7, 30 or 90 days, recorded only on
    this computer, and it can be turned off or erased in Settings.
  • Pick up where you left off after an unexpected exit: after a crash or force quit, Home offers
    the Pull Request you were viewing with “Resume” or “Dismiss”, opening nothing by itself, and the
    error screen reopens the same PR before falling back to Home.
  • A smoother first connection and token handling: the permissions list says why each one is
    needed, pasting a PR link fills in the organization and opens that PR, connection errors say what
    to do, a banner flags a rejected or soon-to-expire token with “Replace token”, and the update
    check resumes as soon as the network is back.
  • Request limits are respected and visible: when Azure DevOps asks to slow down, the account’s
    automatic refresh pauses until the announced time and a discreet notice says until when, as it now
    also does for GitHub and GitLab, without any action being retried by itself.
  • Find, copy and print in a very large diff: Stream find finds every match even off screen,
    copying gives all the selected text, a file or hunk can be copied and printed on light pages, and
    in a list of more than 400 files the arrow keys respond at once.
  • Markdown files now render, Mermaid diagrams included: in a pull request and in the Code space, a
    README or a document shows formatted, with a Preview · Diff / Preview · Source switch remembered on
    your computer, a contents list from three headings on, the file’s changes marked in the preview (one
    click takes you to the diff), working links and images from the repository, and nothing is ever
    written from the preview: raw HTML is never run and remote images are never loaded.

Improvements

  • “Open history” from a PR file: the file menu opens the Code space on that file with the history
    panel already showing, instead of a plain “Open in the Code space”.
  • Home: one queue, organized by whose turn it is: My queue reads in sections (your turn, others’
    turn, resume, elsewhere in the project), appears as soon as the list is read, says whose turn it
    is and for how long, and the more compact banner carries refresh and the queue scope.
  • Accessibility: easier to read, high contrast and keyboard everywhere: text, state colors and
    focus read better in both themes and follow the system contrast and transparency settings, text
    scales up to 200% without overlap, menus, tabs, lists and settings can be walked with the arrow
    keys, screen readers announce the outcome of actions, and shortcuts follow your keyboard layout.
  • The PR window opens faster, without a loading screen: a PR opened in another window appears
    right away with its title, files and diff, and the loading screen only shows if opening really
    drags.
  • Loading screen: the logo assembles as the app starts: the two halves of the “D” come together
    step by step in place of the progress bar, stay apart on failure, and give way to dots when
    animations are reduced.
  • PR header: no more wasted space in a narrow panel: the status chips and the build line use the
    full width instead of staying offset in the title column.
  • The general search gets a new shortcut: it moves to Cmd+Shift+P (Ctrl+Shift+P on Windows) to
    free the editor’s sequences, your custom shortcut is kept, and the hover for the symbol under the
    cursor becomes available.
  • macOS: 120 Hz smoothness on ProMotion displays: windows refresh at the display’s native rate
    for smoother scrolling and animations, at the cost of a little more battery.
  • Review panel: Threads and Chat are distinguishable: the Chat icon now differs from Threads,
    and every icon-only tab shows its name and shortcut on hover.
  • PR threads: “3 / 7” in the list: the number of unresolved threads is shown against the total
    in the list row, and screen readers say “3 unresolved threads out of 7”.
  • Fewer requests, less memory and less piled-up data: the PR list is no longer re-read while the
    window is hidden or more often than needed, comment images are released from memory, and old
    ticks, drafts and checklists untouched for 180 days are removed.
  • More accurate labels in Team, Repositories and Code: the Team refresh picker reads “Refresh:
    manual”, the Repositories pill says “2 mine”, and the Pull Requests card in Code is plural.
  • Settings and setup wizard redone: wider, better organized, quicker to finish: Settings open
    wide, organized in six groups (You, Display, Review, Search and AI, Activity, System) with a
    search that shows each setting’s path and a “Changed” filter; every setting says when it applies
    (Immediately, Next PR, Next launch, When Settings close), resets to its default in one click
    (undoable for 10 s), all on/off settings are “On / Off” switches, second-order settings are
    folded into “Advanced settings”, Appearance and Text and fonts show a live preview with “Apply
    now”, “Code editor” becomes “Diff and editor”, and the palette jumps straight to a page or a
    setting. The wizard takes five steps (Connection, Your work, Appearance, Options, All set): it
    greets you by name, pre-fills the opening space from your role, splits notifications, AI and
    statistics into three cards (statistics never ticked by default), recaps the result with “Edit”
    and suggests reading the first PR in My queue; a first connection goes from 10 to 6 clicks and
    from about 11 s to 8 s.
  • Back and Forward with the mouse: the side buttons of your mouse go back and forward everywhere in
    the app, as in VS Code or a browser.
  • Fast mode: “Retry” detects git right away: once git is installed, clicking “Retry” turns fast mode
    on without restarting Diffwright.

Fixes

  • Notices no longer shift the interface: the error or token-expiry message now floats at the top
    center above the screen instead of pushing all content down, and closes with one click.
  • Build card: “Satisfied” becomes a ✓ icon: shorter and easier to read, with the word “Met” as a
    tooltip and for screen readers.
  • Settings: the “Modified” tracking now sees every setting: the counter, the row dot and the page
    reset cover settings stored on the application side (news, languages, review flow, test folders, Fast
    mode, pre-analysis, offline, statistics), and the more compact Settings notices no longer shift the
    app beneath the dialog.
  • Settings and wizard: comfortable at 900×600 and with text at ×2: the sidebar and wizard scroll cues
    show in the smallest window, icons follow the text size, the wizard title no longer moves between
    steps, Settings opens on the page title, and the command palette is stricter on short queries.
  • The diff no longer jumps when the File / Stream toggle arrives: its slot is reserved as soon
    as the PR opens, and the failing-test preview no longer overflows the diff width.
  • Build and failing tests no longer contradict each other: the card said “Build failed” while
    the details said “In progress”, and a test’s analysis read the PR head’s code instead of the
    build’s.
  • Larger text: no more squeezed columns or badges over icons: with text at ×1.5 or ×2, labels
    were cut off and the diff dropped to about 450 px, whereas the layout now follows the text size
    (strip lists, drawer panels, unified diff) with no change at normal size.
  • Keyboard focus is no longer lost after an action: after opening a PR, a commit, a token
    replacement, a Settings button or a “Retry”, focus restarted from the top of the page, and it now
    goes where expected.
  • Screen readers: no more missing, repeated or misplaced announcements: merge, draft publishing,
    reviewers, failures and notices were silent or announced several times, and column handles, thread
    menus and cards belonged to no region.
  • Small legibility flaws in Code, Team and Settings: some labels were clipped (wizard steps, “1
    fi…”, BETA badge), some targets were too small and brackets unreadable in high contrast, and the
    blame, image preview and Markdown table were not usable from the keyboard.
  • With a read-only token, no write action is offered anymore: an account without write access
    still showed complete, abandon, publish, edit or delete, and these actions and their shortcuts are
    now absent or refused without sending anything.
  • GitHub and GitLab: each platform speaks its own vocabulary: the Pull requests space, Home,
    Team, help and the connection wizard said “Pull Request”, “build” or “vote” where GitHub speaks of
    checks and reviews and GitLab of pipelines, Merge Requests and approvals.
  • GitHub and GitLab: a truncated list is no longer shown as complete: on a very busy PR, threads
    and checks beyond the page cap were silently ignored and CI could look “all green”, whereas a
    “Partial list” mention now appears.
  • A write rejected by a server error is described accurately: after a server error on an action
    (comment, vote, merge…), a message announced a lost reply or invited you to retry, whereas it now
    asks you to check on the platform before trying again.
  • PR list: no more false “No active Pull Request”: when the request limit was reached or the
    read failed, the list stayed on an endless skeleton or spoke of missing PRs, and it now states the
    pause or the failure.
  • Merge and reviewers: one blocker count, up to date after every action: the Merge card’s header
    and note contradicted each other after a vote or a draft publication, and adding a reviewer was
    not possible from the keyboard.
  • Pinned PR windows: “Retry” and history preserved: a window in error asked you to close it with
    no button to do so, and the main window and the pinned one erased each other’s last visits, resume
    point and deleted history.
  • Notices no longer cover a button: notices (token, request limit, unreadable settings) hid the
    beta banner’s “Got it” or the actions of “Start with”, and they now stack under the title bar.
  • Code space: keyboard and commit polish: committing right after the last keystroke was lost,
    “Edit” and “Blame” disappeared on a short-named branch, and the symbol hover’s “Copy” button
    stayed in English.
  • Diff: no more internal error when returning to a PR in a narrow window: on macOS, returning to
    a PR in a narrow window could show an internal error.
  • macOS: the title bar is properly aligned: the account chip touched the green window button and
    the window buttons sat 6 to 8 px below the bar’s center.
  • Review tab: the “private until…” note is clear: it read like “Complete the PR…” and the
    blockers reason was cut off by an ellipsis, whereas it now reads in full.
  • Team: signals and PRs counted correctly: the “N signals to check” heading did not count every
    displayed signal, an analysis failure was reported twice, and two PRs with the same number in two
    repositories were mixed up.
  • Person names without the organization suffix everywhere: “Noah Martin (Contoso)” showed up
    that way in threads, comments, reviewers and Home, and now shows as “Noah Martin”, with the full
    name kept in a tooltip.
  • A PR’s test status no longer shows on the same-numbered PR in another repository: on GitHub
    and GitLab, a verdict recorded on #12 of one repository also appeared on #12 of another, and the
    “To test” counter was wrong.
  • Changed files: “Detect renames” no longer outlives a comparison change: the result stayed on
    screen after a Delta / Cumulative switch or an iteration or commit change, with rows that no
    longer opened anything.
  • “Set up Diffwright” card: “Later” really snoozes: “Later” did not hide the card, which now
    hides for 7 days, and its icon carried an AI mark that is reserved for AI features.
  • Auto-review: a failed review is no longer retried every 5 minutes: a PR whose automatic review
    failed used up the assistant’s quota on every poll, whereas it is now retried after 10 then 30
    minutes before being dropped for the session.
  • Azure DevOps notifications: PRs beyond a project’s first 100 are found: on a large project,
    PRs beyond the hundredth escaped notifications, and they are now read page by page.
  • An AI suggestion is no longer published twice: clicking “Publish” on the same suggestion from
    the diff then the Review panel, or by double click, created two identical comments visible to the
    team, and a single thread is now created.
  • No booby-trapped repository command or content run or sent to the AI by mistake: opening
    Settings ran a test of the turned-off AI assistant, a booby-trapped document or comment could load
    a remote script, a repository command ran without the plan you saw, and a PR’s text could be taken
    for an instruction by the AI.
  • App crash: running AI assistants are stopped: after a crash during a review or a question, the
    assistant kept running in the background and using up your quota.
  • A failed save is no longer silent: a full disk or a locked file led you to believe drafts,
    reviewed files and settings were saved, a switch stayed on its new value, and an unreadable review
    history blocked everything, whereas a message now warns you.
  • Large files: accurate +/− counts and risk beyond 2,000 lines: a file with scattered edits was
    counted as entirely deleted then re-added, inflating its bar and risk score, and the count is now
    exact and faster.
  • Azure DevOps: PRs with more than 5,000 files: an iteration’s file list was silently truncated,
    with a wrong “reviewed X/N”, and a list that is too long is now flagged.
  • Images and binary files properly centered: an image, or the notice of a binary file, was not
    centered in its area and now is.