Page MenuHomePhabricator

Make omitting "value" from a transaction description an explicit error
ClosedPublic

Authored by epriestley on Apr 27 2020, 8:14 PM.
Tags
None
Referenced Files
F14895387: D21176.id50427.diff
Sun, Feb 9, 9:07 AM
F14895386: D21176.id50426.diff
Sun, Feb 9, 9:07 AM
F14895385: D21176.id.diff
Sun, Feb 9, 9:07 AM
F14895384: D21176.diff
Sun, Feb 9, 9:07 AM
Unknown Object (File)
Sat, Feb 8, 6:02 AM
Unknown Object (File)
Sat, Feb 8, 1:16 AM
Unknown Object (File)
Fri, Feb 7, 3:14 AM
Unknown Object (File)
Fri, Jan 31, 1:39 PM
Subscribers
None

Details

Summary

See PHI1710. Until D21044, some transactions could omit "value" and apply correctly. This now throws an exception when accessing $xaction['value']. All transactions are expected to have a "value" key, so require it explicitly rather than implicitly.

Test Plan

Submitted a transaction with a "type" but no "value". After D21044, got a language-level exception. After this change, got an explicit exception.

Diff Detail

Repository
rP Phabricator
Branch
edit1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 24245
Build 33394: Run Core Tests
Build 33393: arc lint + arc unit