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)
Tue, Jan 21, 11:44 AM
Unknown Object (File)
Fri, Jan 17, 7:58 PM
Unknown Object (File)
Mon, Jan 13, 12:29 PM
Unknown Object (File)
Fri, Dec 27, 8:08 PM
Unknown Object (File)
Dec 17 2024, 4:58 PM
Unknown Object (File)
Dec 16 2024, 5:48 AM
Unknown Object (File)
Dec 9 2024, 7:42 PM
Unknown Object (File)
Dec 9 2024, 4:45 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable