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
Unknown Object (File)
Mon, Nov 25, 2:33 AM
Unknown Object (File)
Wed, Nov 20, 5:28 PM
Unknown Object (File)
Mon, Nov 18, 5:11 PM
Unknown Object (File)
Thu, Nov 14, 6:56 AM
Unknown Object (File)
Thu, Nov 14, 4:04 AM
Unknown Object (File)
Sun, Nov 10, 8:07 AM
Unknown Object (File)
Thu, Oct 31, 6:29 AM
Unknown Object (File)
Wed, Oct 30, 6:46 AM
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