Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • I ended up doing something of a mix between what you and Radim suggested - having the states resolve their own dependencies, and the states that fall outside of the hierarchy registering listeners on the user service object Commented Dec 13, 2013 at 12:31
  • 1
    @David any way we can see what you ended up doing? I'm running into something similar Commented Feb 19, 2014 at 18:04
  • 2
    @SonicTheLichen Sure, I'll put a fiddle together today to show you Commented Feb 20, 2014 at 17:06
  • 3
    New example: jsfiddle.net/2ebZj/1 now, I can just use ResolveProvider.User to require each state to check the user is logged in. I also have a few other commonly used resolutions in my ResolveProvider Commented Feb 20, 2014 at 19:29
  • 1
    @SonicTheLichen realized I didn't @ you so here's this comment just in case Commented Feb 21, 2014 at 0:38