Page MenuHomePhabricator

Make event-triggered actions more aware of application access
ClosedPublic

Authored by epriestley on Oct 19 2013, 10:35 PM.
Tags
None
Referenced Files
F15928850: D7365.id16610.diff
Mon, Jun 2, 5:05 AM
F15924864: D7365.id.diff
Mon, Jun 2, 2:36 AM
F15924863: D7365.diff
Mon, Jun 2, 2:36 AM
F15919402: D7365.id16610.diff
Sun, Jun 1, 10:28 PM
F15919401: D7365.id16581.diff
Sun, Jun 1, 10:28 PM
F15911371: D7365.id.diff
Sun, Jun 1, 5:18 PM
Unknown Object (File)
Sat, May 31, 9:00 PM
Unknown Object (File)
Sat, May 31, 8:58 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
Restricted Maniphest Task
Commits
Restricted Diffusion Commit
rP8994a81b3538: Make event-triggered actions more aware of application access
Summary

Fixes T3675.

  • Maniphest had a couple of old non-event listeners; move them to events.
  • Make most of the similar listeners a little more similar.
  • Add checks for access to the application.
Test Plan
  • Viewed profile, project, task, revision.
  • Clicked all the actions.
  • Blocked access to various applications and verified the actions vanished.

Diff Detail

Branch
appevent2
Lint
Lint Passed
Unit
Tests Passed

Event Timeline

btrahan added inline comments.
src/applications/phriction/event/PhrictionActionMenuEventListener.php
18

maybs this should be upgraded to some getObject?

It seems like that is standard-ish and then we get type checking which will give us other guarantees about object. Just maybs for someday thought

src/applications/phriction/event/PhrictionActionMenuEventListener.php
18

Yeah, we could probably take a pass on PhabricatorEvent at some point and unify some of it. I'd guess getObject() is probably reasonable at a minimum.