Injecting resolves into directive controllers

Question

I'm using AngularUI router (0.2.13) and have a state defined as such

.state('foo', { 
           template:'<div some-directive></div>', 
           resolve:{
               foo:function(SomeService){
                   return SomeService.something().promise;
               }
           })

and a directive like this:

app.directive('someDirective', function(){
     return {
         controller: function(data) {
           // I want `data` to be injected from the resolve... 
           // as it would if this was a "standalone" controller
         }
     }
})

but this doesn't work - the data parameter causes an UnknownProvider error. Defining the directive controller independently and setting it by name in the directive has the same result.

I more or less get why this is happening, but have two questions:

1. is there a way to do what I'm trying to do?
2. should I be trying to do it, or have I slipped into an antipattern here?

Answer 1

They simplified the api. See this thread:

https://github.com/angular-ui/ui-router/issues/2664#issuecomment-204593098

in 0.2.19 we are adding $resolve to the $scope, allowing you to do "route to component template" style

template: <my-directive input="$resolve.simpleObj"></my-directive>,

Answer 2

You can't use resolves in directives, but you can pass the result resolved in the state down to the directive which I think accomplishes what you're looking for.

You'd want to update your state definition to include a controller and set a parameter on the directive:

.state('foo', { 
   template:'Test<div some-directive something="foo"></div>',
   url: 'foo',
   resolve:{
       foo:function(SomeService){
           return SomeService.something();
       }
   },
   controller: function($scope, foo){
     $scope.foo = foo;
   }
})

Then update the directive to use this parameter:

.directive('someDirective', function(){
     return {
         controller: function($scope) {
           // I want `data` to be injected from the resolve... 
           // as it would if this was a "standalone" controller
           console.log('$scope.something: '+ $scope.something);
         },
         scope: {
           something: '='
         }
     };
})

Here's a sample plunker: http://plnkr.co/edit/TOPMLUXc7GhXTeYL0IFj?p=preview