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
F15429250: D7365.id16610.diff
Mon, Mar 24, 1:22 AM
F15424506: D7365.id.diff
Sat, Mar 22, 10:46 PM
F15412251: D7365.id16581.diff
Wed, Mar 19, 12:01 PM
F15398605: D7365.diff
Mon, Mar 17, 12:49 AM
F15334886: D7365.id.diff
Sat, Mar 8, 1:01 PM
Unknown Object (File)
Thu, Feb 27, 3:20 AM
Unknown Object (File)
Thu, Feb 27, 3:20 AM
Unknown Object (File)
Thu, Feb 27, 3:20 AM
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

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

btrahan added inline comments.
src/applications/phriction/event/PhrictionActionMenuEventListener.php
18โ€“20

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โ€“20

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.