Page MenuHomePhabricator

Get rid of "throwResult()" for control flow in MFA factors
ClosedPublic

Authored by epriestley on Jan 25 2019, 6:07 PM.
Tags
None
Referenced Files
F14397297: D20035.diff
Sun, Dec 22, 10:09 AM
Unknown Object (File)
Fri, Dec 20, 11:06 AM
Unknown Object (File)
Fri, Dec 20, 2:51 AM
Unknown Object (File)
Sat, Dec 14, 8:01 PM
Unknown Object (File)
Sat, Dec 14, 3:27 PM
Unknown Object (File)
Sun, Dec 8, 3:32 PM
Unknown Object (File)
Sun, Dec 8, 2:28 AM
Unknown Object (File)
Sun, Dec 8, 12:12 AM
Subscribers
None

Details

Summary

Depends on D20034. Ref T13222. This is just cleanup -- I thought we'd have like two of these, but we ended up having a whole lot in Duo and a decent number in SMS. Just let factors return a result explicitly if they can make a decision early. I think using instanceof for control flow is a lesser evil than using catch, on the balance.

Test Plan

grep, went through enroll/gate flows on SMS and Duo.

Diff Detail

Repository
rP Phabricator
Branch
mfa5
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 21698
Build 29597: Run Core Tests
Build 29596: arc lint + arc unit