Petr Pchelko bc6f7e4bdc Make User implement Authority ... Ideally, only User associated with the global request should be associated with UserAuthority. For a random user instance, not the current performer, checking permissions should be based solely on user groups and perhaps an existing block. Right now however, PermissionManager is coupled with global request, so we still instantiate a UserAuthority for non-current users. This mimics the behaviour we've had before. As we refactor PermissionManager, we will be able to replace Authority implementation in this case, or even entirely prohibit non-performer authority. Bug: T271459 Depends-On: Iebf2dca34eea751391d9740443c195287399aa5c Change-Id: Ib094e498fd883db23f2763f171281b1c9e99217e		2021-01-19 18:08:12 -06:00
..
api	Inject UserCache into ApiUnblock	2020-11-19 18:46:09 +00:00
includes	Make User implement Authority	2021-01-19 18:08:12 -06:00
languages