Repository navigation
v0.43.0
What's changed
Open a Files row with a click anywhere on it
In the Files listing a folder or file only opened from its name, so a
click on the rest of the row did nothing. Native Repos opens the row from
anywhere on it. The listing's Table now uses singleClickActivation and
opens the entry (submodules still don't open). The Table leaves clicks on
links and buttons alone, so the name link, the commit link and the row's
"..." menu behave as before (checked in the mock harness: the menu opens
and the address stays the same).
Let Blame use the card's full width
Blame showed the code in a narrow strip that scrolled sideways, with
empty space to its right. The card's content is a flex row and the blame
block inside it wasn't allowed to grow, so it kept the width of its first
render, and Monaco (which follows its container) stayed that narrow. The
block now grows to fill the card: measured in the mock harness at 1237px
of 1237px, against 932px before.
Release 0.42.1
A click anywhere on a Files row opens it, as in native Repos, and Blame
uses the card's full width instead of scrolling the code sideways in a
narrow strip.
Draft and edit releases in a side panel
"Draft a new release" and "Edit release" replaced the whole Releases
tab with a form, which isn't how native ADO handles create and edit: it
opens them over the page. The form is now an azure-devops-ui Panel
(large) titled with the action and the repository, over the releases
list, or over the release itself when editing. Cancel, Save draft and
the primary button (Publish release / Update release) sit in the
panel's footer and show "Saving…" while they work. Closing the panel is
Cancel, so a changed form still asks before discarding, and the panel
can't be dismissed while a save is running.
The address still carries releaseForm (and release when editing), so a
link or a refresh opens the panel again. The detail view now stays
behind the panel when editing; with releaseForm=new the release key is
only the tag to preset (Tags' "Create release"), so the list stays
behind it. Nothing hand-rolled.
Release 0.42.2
Drafting and editing a release happen in a side panel over the page,
as native ADO's create and edit forms do. Also in this release (0.42.1
was never published): a click anywhere on a Files row opens it, and
Blame uses the card's full width.
Go back from a release with the Header's back button
A release's own page had an "All releases" button above the card.
Native detail pages go back with the Header's back button, as our PR,
Branch policies and alert pages already do, so the Tags & Releases
Header now has one ("Back to releases") while a release is open, and
the button is gone. The release card keeps its own title, so the Header
keeps the hub's.
Lay out New pull request as native does
The New pull request page put the title and description on the left,
GitHub-style side panels for reviewers, work items, tags and the rest on
the right, the Files and Commits preview underneath and the Create
button under the description. Native ADO has the branches under the
title, then Overview / Files / Commits tabs (with counts), and Overview
is a single card: Title, Description (with "Add commit messages" beside
its label), Reviewers, Work items to link (with a count and "Clear
all"), Tags, then "Set auto-complete" and the Create split button at the
card's foot, right-aligned.
The page now follows that. The card is 960px at most, as native's. The
reviewer, work item and tag pickers are always-open fields in the card
instead of panels with an Add button; picking adds the item beneath and
the field empties for the next one. GitHub's Assignees, Milestone and
Projects, which native has no counterpart for, follow native's fields
in the same style. "Add commit messages" appends the commits' subjects
to the description as a list. The Files count is loaded with the
comparison (the Files tab reuses the cached answer). The header's back
button is gone, as native has none.
AddSearch, PeopleAdd and the pickers built on them take an inline
flag for this: no Cancel button and no focus grab; the PR page's panels
keep the old behaviour. Nothing hand-rolled; the label actions are
Buttons positioned beside FormItem labels.
Release 0.43.0
New pull request is laid out as native's: Overview / Files / Commits
tabs and one card with the form and Create at its foot. Drafting and
editing a release happen in a side panel, a release page goes back with
the Header's back button, a click anywhere on a Files row opens it, and
Blame uses the card's full width. (0.42.1 and 0.42.2 were never
published.)
Bring New pull request's fields closer to native
Side by side with native's New pull request, ours still differed in how
the fields behaved:
- Reviewers and Assignees are now azure-devops-ui's multi IdentityPicker:
the chosen people sit inside the field as persona chips with an x and a
+, as native's Reviewers does, instead of a search box with a list
underneath. Tags and Projects are TagPickers with their pills inside
the field (tags keep GitHub's label colours). - Description follows native's order: the text, a character counter
(GitHub's 65,536 limit; over it, Create is blocked with a reason),
"Markdown supported." and how to link work items, the formatting
toolbar below the text, then a live preview rendered by GitHub. The
preview waits for typing to pause (600ms). CommentBox gains
toolbarBelow and footer for this; the release form's preview moves to
MarkdownPreview.tsx and is shared. - Linked work items read as native's: type icon, "Type ID: title"
linking to the item, then "Updated , " with the state's
own colour, and x. The work item lookup now also asks for
System.ChangedDate, and the type list's state colours are kept.
The PR page's own reviewer and tag panels are unchanged. Nothing
hand-rolled.
Full changelog: v0.42.0...v0.43.0