Page MenuHomePhabricator

Transactions - make sure to do fancy remarkup stuff on edit too
ClosedPublic

Authored by btrahan on Dec 2 2014, 11:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 25, 1:06 AM
Unknown Object (File)
Thu, Apr 11, 8:47 AM
Unknown Object (File)
Apr 1 2024, 10:26 PM
Unknown Object (File)
Mar 30 2024, 3:21 PM
Unknown Object (File)
Mar 13 2024, 2:03 PM
Unknown Object (File)
Mar 7 2024, 12:59 PM
Unknown Object (File)
Feb 14 2024, 7:53 AM
Unknown Object (File)
Feb 7 2024, 11:18 PM
Subscribers

Details

Summary

Fixes T6648. We do some automagical hotness based on the text you enter in remarkup textareas - e.g. adding projects or mentioning other objects. Refine the code here so that even when just editing a comment we build these transactions and apply them.

Test Plan

edited a comment and noted new mentions and projects showed up appropriately...!

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

btrahan retitled this revision from to Transactions - make sure to do fancy remarkup stuff on edit too.
btrahan updated this object.
btrahan edited the test plan for this revision. (Show Details)
btrahan added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php
1129–1134

Maybe just do something like filter out the object which === $xaction explicitly, in case expandSupportTransactions() ever messes around with transaction order, but this seems generally reasonable.

This revision is now accepted and ready to land.Dec 3 2014, 12:34 AM
btrahan edited edge metadata.
  • use === to lower brittleness
This revision was automatically updated to reflect the committed changes.