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)
Wed, Apr 17, 2:53 PM
Unknown Object (File)
Thu, Apr 4, 8:37 AM
Unknown Object (File)
Sun, Mar 31, 11:33 AM
Unknown Object (File)
Sun, Mar 31, 6:50 AM
Unknown Object (File)
Feb 11 2024, 5:58 AM
Unknown Object (File)
Dec 15 2023, 8:40 AM
Unknown Object (File)
Nov 30 2023, 4:20 AM
Unknown Object (File)
Nov 17 2023, 6:02 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable