Page MenuHomePhabricator

Remove the "willApplyTransactions()" hook from ApplicationTransactionEditor
ClosedPublic

Authored by epriestley on Dec 18 2018, 10:34 PM.
Tags
None
Referenced Files
F19095687: D19909.id.diff
Thu, Dec 4, 5:51 AM
F19091139: D19909.diff
Wed, Dec 3, 1:43 PM
F19073992: D19909.diff
Mon, Dec 1, 3:46 AM
F19073977: D19909.diff
Mon, Dec 1, 3:43 AM
F19073960: D19909.diff
Mon, Dec 1, 3:40 AM
F18885608: D19909.id47596.diff
Nov 7 2025, 3:30 AM
F18857139: D19909.diff
Nov 1 2025, 1:29 PM
F18844949: D19909.id.diff
Oct 29 2025, 8:32 AM
Subscribers
None

Details

Summary

Depends on D19908. Ref T13222. In D19897, I reordered some transaction code and affected the call order of willApplyTransactions().

It turns out that we use this call for only one thing, and that thing is pretty silly: naming the raw paste data file when editing paste content.

This is only user-visible in the URL when you click "View Raw Paste" and seems exceptionally low-value, so remove the hook and pick a consistent name for the paste datafiles. (We could retain the name behavior in other ways, but it hardly seems worthwhile.)

Test Plan
  • Created and edited a paste.
  • Grepped for willApplyTransactions().

Note that EditEngine (vs ApplicationTransacitonEditor) still has a willApplyTransactions(), which has one callsite in Phabricator (in Calendar) and a couple in Instances. That's untouched and still works.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable