Page MenuHomePhabricator

Remove the "willApplyTransactions()" hook from ApplicationTransactionEditor
ClosedPublic

Authored by epriestley on Dec 18 2018, 10:34 PM.
Tags
None
Referenced Files
F14063909: D19909.diff
Mon, Nov 18, 8:47 PM
F14011168: D19909.id.diff
Thu, Oct 31, 8:26 PM
F14005377: D19909.diff
Sun, Oct 27, 12:21 PM
F13999668: D19909.id47524.diff
Thu, Oct 24, 4:19 PM
F13980310: D19909.id47596.diff
Oct 19 2024, 9:43 AM
F13972117: D19909.id47524.diff
Oct 17 2024, 5:13 PM
Unknown Object (File)
Oct 9 2024, 11:02 AM
Unknown Object (File)
Sep 6 2024, 4:47 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