Page MenuHomePhabricator

Stop evaluating Herald rules when writing "someone mentioned this somewhere else." transactions
ClosedPublic

Authored by epriestley on Mar 28 2018, 10:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 27, 7:39 PM
Unknown Object (File)
Tue, Nov 19, 4:08 AM
Unknown Object (File)
Tue, Nov 12, 12:21 PM
Unknown Object (File)
Tue, Nov 12, 10:39 AM
Unknown Object (File)
Tue, Nov 12, 9:44 AM
Unknown Object (File)
Tue, Nov 12, 9:25 AM
Unknown Object (File)
Tue, Nov 12, 9:01 AM
Unknown Object (File)
Sat, Nov 9, 3:03 PM
Subscribers
None

Details

Summary

Ref T13114. See PHI510. Firing Herald on mentioned objects tends to feel arbitrary and can substantially slow down edits which mention many objects.

Test Plan

Mentioned tasks on other tasks; verified that the normal path is hit normally, the new Herald-free path is hit on the mentioned object, and both still work fine and show up in the timeline.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Although I'm focusing on "mentions" here, "inverse edge edits" apply more broadly to any situation where an object is the far end of a link, so Ref Xyz., Fixes Xyz., Depends on Dxxx., "Edit Parent Tasks", etc. will also hit this logic. I think this is appropriate in all cases -- it doesn't feel to me like any of these "another object is now related to this object somehow" changes should be firing Herald updates on the target.

This revision was not accepted when it landed; it landed in state Needs Review.Mar 28 2018, 10:35 PM
This revision was automatically updated to reflect the committed changes.