client/web: Add UI elements for Azure DevOps auth provider#47865
Conversation
Bundle size report 📦
Look at the Statoscope report for a full comparison between the commits 47669b0 and 8e24306 or learn more. Open explanation
|
355a7d4 to
da07d75
Compare
sashaostrikov
left a comment
There was a problem hiding this comment.
LGTM, left a comment about changing default behaviour for external account URL/display name
There was a problem hiding this comment.
sg lint -fix format wanted to make this change.
There was a problem hiding this comment.
Oh I know why. Will fix.
There was a problem hiding this comment.
Hmmm, that seems like a bug though
mrnugget
left a comment
There was a problem hiding this comment.
Very good PR description!
There was a problem hiding this comment.
Hmmm, that seems like a bug though
Fixed now. Was some leftover of trying to restore it to its original form while working on Alex's suggestion. |
Incorrectly using Kind instead of Type.
85b08cd to
33a56da
Compare
Snapshot testing for the win!
|
Codenotify: Notifying subscribers in CODENOTIFY files for diff 8e24306...47669b0.
|
This PR does a few related things:
Changes the code to display connected account information to use thedisplayNameinstead of theurlpropertyThis change was required because the closest thing to an account page (equivalent of github.com/indradhanush for example) for ADO that I found was: https://aex.dev.azure.com/me. Which shows the currently logged in user, but I couldn't find a permanent URI for a user. As a result the connected account information could not be displayed if we continued to display it against the check for a non-nullurlin the frontend codeAdditionally, presence of a display name as the primary check makes more sensecasehandling forazuredevops👉 Finally, it fixes a bug (discovered as a result of implementing this) with the
parseProviderwhere I was incorrectly using theKindinstead ofType.Sidenote: Since both are strings and the only difference is that the former is in
UPPERCASEwhile the latter is inlowercase, this is an easy mistake to make. The real fix should be that these should be custom types so that methods that accept these as an argument get the powers of type checking. Expect a follow up PR.Test plan
Sign in page (notice the cute icon)
Accounts security page, not connected account
Accounts security page, connected account
Account disconnection prompt
App preview:
Check out the client app preview documentation to learn more.