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
F19083304: D21176.id50427.diff
Dec 2 2025, 12:33 PM
F19018528: D21176.id.diff
Nov 23 2025, 11:26 AM
F19011036: D21176.diff
Nov 22 2025, 7:24 AM
F18985460: D21176.id50426.diff
Nov 17 2025, 1:03 PM
F18871481: D21176.id50426.diff
Nov 4 2025, 10:58 PM
F18850386: D21176.diff
Oct 30 2025, 4:19 PM
F18820841: D21176.id.diff
Oct 22 2025, 5:30 PM
F18812590: D21176.diff
Oct 20 2025, 10:39 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