Paths

Table of Contentst

Differential D21176

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

Authored by epriestley on Apr 27 2020, 8:14 PM.

Tags

None

Subscribers

None

Details

Reviewers: None
Commits: rPc176a3038a4b: (stable) Make omitting "value" from a transaction description an explicit error
rPb5bed7b0fa87: Make omitting "value" from a transaction description an explicit error

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

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

epriestley created this revision.Apr 27 2020, 8:14 PM

Harbormaster completed remote builds in B24245: Diff 50426.Apr 27 2020, 8:15 PM

This revision was not accepted when it landed; it landed in state Needs Review.Apr 27 2020, 8:15 PM

epriestley requested review of this revision.

Closed by commit rPb5bed7b0fa87: Make omitting "value" from a transaction description an explicit error (authored by epriestley). · Explain Why

This revision was automatically updated to reflect the committed changes.

epriestley added a commit: rPb5bed7b0fa87: Make omitting "value" from a transaction description an explicit error.

epriestley added a commit: rPc176a3038a4b: (stable) Make omitting "value" from a transaction description an explicit error.

Revision Contents
Changeset List

Path

Size

src/

applications/

transactions/

editengine/

PhabricatorEditEngine.php

10 lines

Diff 50427

src/applications/transactions/editengine/PhabricatorEditEngine.php

Loading...