Page MenuHomePhabricator

Remove deprecated Maniphest "Can Edit <Specific Property>" capabilities
ClosedPublic

Authored by epriestley on Aug 14 2018, 5:52 PM.
Tags
None
Referenced Files
F15431146: D19581.id46812.diff
Mon, Mar 24, 10:47 AM
F15417785: D19581.id46812.diff
Thu, Mar 20, 6:31 PM
F15412414: D19581.diff
Wed, Mar 19, 12:55 PM
F15379895: D19581.id46835.diff
Fri, Mar 14, 12:02 AM
F15354408: D19581.id.diff
Tue, Mar 11, 3:49 AM
Unknown Object (File)
Fri, Feb 28, 10:51 AM
Unknown Object (File)
Feb 21 2025, 3:38 PM
Unknown Object (File)
Feb 9 2025, 6:18 AM
Subscribers

Details

Summary

Depends on D19579. Fixes T10003. These have been deprecated with a setup warning about their impending removal for about two and a half years.

Ref T13164. See PHI642. My overall goal here is to simplify how we handle transactions which have special policy behaviors. In particular, I'm hoping to replace ApplicationTransactionEditor->requireCapabilities() with a new, more clear policy check.

A problem with requireCapabilities() is that it doesn't actually enforce any policies in almost all cases: the default is "nothing", not CAN_EDIT. So it ends up looking like it's the right place to specialize policy checks, but it usually isn't.

For "Disable", I need to be able to weaken the check selectively (you can disable users if you have the permission, even if you can't edit them otherwise). We have a handful of other edits which work like this (notably, leaving and joining projects) but they're very rare.

Test Plan

Grepped for all removed classes. Edited a Maniphest task.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable