Page MenuHomePhabricator

Implement "Test Plan" as a CustomField
ClosedPublic

Authored by epriestley on Feb 20 2014, 6:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 3:48 PM
Unknown Object (File)
Fri, Dec 20, 10:04 AM
Unknown Object (File)
Fri, Dec 13, 3:28 AM
Unknown Object (File)
Fri, Nov 29, 9:56 PM
Unknown Object (File)
Fri, Nov 29, 1:53 AM
Unknown Object (File)
Tue, Nov 26, 5:25 PM
Unknown Object (File)
Nov 17 2024, 8:48 PM
Unknown Object (File)
Nov 15 2024, 12:12 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
Restricted Maniphest Task
Commits
Restricted Diffusion Commit
rP05f2ab32d8cc: Implement "Test Plan" as a CustomField
Summary

Ref T3886. Moves some of the "required" logic to the base class ("DifferentialCoreField") so Title and Test Plan can share it.

Test Plan

Edited revisions using "pro" editor, saw test plan transactions.

Diff Detail

Repository
rP Phabricator
Branch
dfield3
Lint
Lint Passed
Unit
Tests Passed

Event Timeline

btrahan added inline comments.
src/applications/differential/customfield/DifferentialCoreCustomField.php
25–30

Nice. Surprised (sort of) PHP doesn't have something native to test this, and / or this hasn't made its way to libphutil yet. Mainly though I am writing this to validate relearning how come empty() is mostly useless.

Yeah, maybe we should write phempty() which means "empty, except for strengths with nonzero string length, like "0"", although sometimes I think we want to call whitespace-only strings "empty" too and other times we don't. Maybe we could always call them "empty" without consequence though -- I can't think of cases offhand where " " is a legitimate nonempty value.

except for strengths

"except for strings" haha