Page MenuHomePhabricator

Move users to modular transactions
ClosedPublic

Authored by epriestley on Aug 13 2018, 9:13 PM.
Tags
None
Referenced Files
F18107911: D19576.diff
Mon, Aug 11, 3:44 AM
F17948893: D19576.id.diff
Thu, Jul 31, 10:18 PM
F17934590: D19576.diff
Wed, Jul 30, 10:41 PM
F17843724: D19576.id46832.diff
Jul 27 2025, 1:16 AM
F17843437: D19576.id46832.diff
Jul 27 2025, 12:53 AM
F17827810: D19576.id46801.diff
Jul 26 2025, 8:33 AM
F17826266: D19576.id.diff
Jul 26 2025, 7:08 AM
F17813151: D19576.diff
Jul 25 2025, 8:01 PM
Subscribers
None

Details

Summary

Ref T13164. See PHI642. I'd like to provide a third-generation user.edit API endpoint and make user.enable and user.disable obsolete before meddling with policy details, even if it isn't full-fledged yet.

Users do already have a transactions table and a Transaction-based editor, but it's only used for editing title, real name, etc. All of these are custom fields, so their support comes in automatically through CustomField extension code.

Realign it for modular transactions so new code will be fully modern. There are no actual standalone transaction types yet so this diff is pretty thin.

Test Plan
  • Grepped for UserProfileEditor.
  • Edited a user's title/real name/icon.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable