Page MenuHomePhabricator

Fix transaction title rendering for AuthenticationConfigs
ClosedPublic

Authored by amckinley on Jul 17 2019, 7:32 PM.
Tags
None
Referenced Files
F19507428: D20655.id49271.diff
Fri, Jan 9, 8:36 PM
F18832019: D20655.id.diff
Oct 25 2025, 6:43 PM
F18785762: D20655.id49271.diff
Oct 14 2025, 11:15 AM
F18768449: D20655.id49271.diff
Oct 8 2025, 3:41 AM
F18704292: D20655.id49272.diff
Sep 28 2025, 6:59 AM
F18671480: D20655.diff
Sep 25 2025, 4:04 AM
F18567145: D20655.id.diff
Sep 9 2025, 3:33 PM
F18178241: D20655.id49271.diff
Aug 16 2025, 1:13 AM
Subscribers

Details

Summary

I was poking around in PhabricatorAuthProviderViewController and noticed that none of the subclass-specific rendering was working. Figured out that no one ever calls PhabricatorAuthProviderConfigTransaction->setProvider(), so instead of adding all those calls, just pull the provider out of the config object.

Test Plan

Before:

Screen Shot 2019-07-17 at 12.28.51 PM.png (541×479 px, 46 KB)

After:
Screen Shot 2019-07-17 at 12.29.00 PM.png (565×579 px, 52 KB)

Diff Detail

Repository
rP Phabricator
Branch
master
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 23139
Build 31776: Run Core Tests
Build 31775: arc lint + arc unit

Event Timeline

This seems very likely to always work properly when we expect it to.

It's possible for a transaction to not have an object but it looks like getObject() throws in this case rather than returning null so we should get a helpful exception even if something bizarre is afoot on some pathway here.

This revision is now accepted and ready to land.Jul 17 2019, 7:39 PM