Page MenuHomePhabricator

Update PhortuneMerchant to Modular Transactions
ClosedPublic

Authored by chad on Mar 30 2017, 3:58 PM.
Tags
None
Referenced Files
F13205256: D17584.diff
Wed, May 15, 1:45 AM
F13188627: D17584.diff
Sat, May 11, 5:23 AM
Unknown Object (File)
Tue, May 7, 8:38 AM
Unknown Object (File)
Fri, May 3, 8:42 AM
Unknown Object (File)
Wed, May 1, 10:49 AM
Unknown Object (File)
Thu, Apr 25, 2:31 AM
Unknown Object (File)
Apr 11 2024, 9:53 AM
Unknown Object (File)
Mar 24 2024, 5:01 PM
Subscribers

Details

Summary

Modernize PhortuneMerchant for Modular Transactions. Also changed the language of "Members" to "Managers", which I think fits better given the power/capability.

Test Plan
  • Create a new Merchant
  • Test not filling in a name, see error
  • Test removing myself, see error
  • Edit an existing Merchant
  • Add new managers
  • Test removing myself, see error
  • Replace Picture
  • Update various fields, contact info, email, footer
  • Verify transactions are now nice and pretty

Diff Detail

Repository
rP Phabricator
Branch
merchant-xaction (branched from master)
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 16386
Build 21796: Run Core Tests
Build 21795: arc lint + arc unit

Event Timeline

epriestley added inline comments.
src/applications/phortune/editor/PhortuneMerchantEditor.php
20–21

You can get rid of these, ModularTransactions figures them out automatically (part of the motivation is that you don't have to edit Editor -- or anything else in the upstream -- to add new transaction types).

src/applications/phortune/storage/PhortuneMerchantTransaction.php
17–19

Can we avoid adding new types of mail tags? Per elsewhere, I believe things will work fine without this code: mail tags are not required, and we didn't have them before.

src/applications/phortune/xaction/PhortuneMerchantInvoiceEmailTransaction.php
73

More correct as if (strlen(...))

76

Technically this one should probably be if (!strlen(...)).

77

newInvalidError

85

This should be newInvalidError().

Usage is:

  • When a field is missing but required, use newRequiredError().
  • When a field is present and invalid, use newInvalidError().

The big difference is that newRequriedError() gets ignored if setContinueOnMissingFields(true) is set on the Editor.

src/applications/phortune/xaction/PhortuneMerchantNameTransaction.php
38

This one is right ("required").

47

newInvalidError

This revision is now accepted and ready to land.Apr 11 2017, 11:45 AM
chad marked 8 inline comments as done.
  • per comments
This revision was automatically updated to reflect the committed changes.