Unable to inject templateProvider with resolved values

[sqs]

A view's templateProvider is unable to be injected with resolved values. The following will fail with an error like Error: [$injector:unpr] Unknown provider: barProvider <- bar.

$stateProvider.state('foo', {
  resolve: {bar: function() { return 123; }},
  views: {
    foo: {
      templateProvider: function(bar) { /* ... */ },
    }
  },
})

I see in resolveState that $view.load only gets some locals to inject. Is there any technical reason why templateProvider couldn't be injected with all of the resolve values in the same way that controller is?

(This is on git master, and I remember seeing the same limitation a couple of months ago.)

[MrOrz]

Just encountered this issue. I need to determine which template to load by looking at the resolved data. However currently in template provider function I cannot access such information.

By the way, in the documentation it mentions that templateProvider can "access to locals", however I could not figure out what this means.

[ksperling]

The reason this works for controller is that the controller is actually instantiated later as a second step, whereas currently $template is actually itself loaded as part of the resolve. It should still be possible to get values to flow through though with some refactoring... essentially a templateProvider would have to be added to the resolve as is (so resolve can inspect it's parameters), rather than called indirectly via $templateFactory.

[MrOrz]

Thanks for the speedy response!

It seems that the controller is the only place we can access resolved data so far.
Maybe the only work-around is to put ng-include in my view, and determine what view to load via ng-include from within the controller.

[ksperling]

I'm not 100% sure this will work, but you should be able to simply have '$template' inside your resolve yourself. It needs to resolve to the loaded template data (not 100% $state won't overwrite that value but give it a try).

[sqs]

Thanks for the tip. I couldn't get that $template trick to work. The value appears to be overwritten. Also, it would not inject another resolved value (which I think depends on #196).

[nateabele]

So, #196 has now been implemented, which enables resolve inheritance, but for this to work, resolve values would have to be resolved synchronously, before templateProvider was executed, which is a performance decrease that many people won't need.

This will be difficult to refactor this effectively, because of the number of abstraction boundaries it crosses.

[jachenry]

I have a similar issue where I'd like to load different views/controllers based on a users role. In order for this to work I'd first have to retrieve the roles from the server (most likely as a resolve property) and inject it into the templateProvider and controllerProvider. Only other option is to define two states, one for each role, and redirect accordingly in the state change handler.

[a-laughlin]

Currently using ui-router 0.2.7 and angular 1.2.6. Currently getting started with angular. I've been debugging what was going on in a UI with multiple named and abstract views. One of the views had a templateProvider fn that returned the template based on resolve values (amidst 8 other values). I didn't know to search for this issue because the templateProvider fn fails silently and I thought the problem was in another part of the code.

Is this failing silently because the return value here is null? I'd be happy to PR an error message if that's a good spot to include it.

[nateabele]

Is this failing silently because the return value here is null? I'd be happy to PR an error message if that's a good spot to include it.

@a-laughlin Yeah, agreed. Thanks.

[a-laughlin]

Cool. It's going to be a few days before I'll be able to get to it, but I'll send a PR when done.

[mklobusnik]

Any idea when this will be fixed. Or what is the way around it?

[hrajchert]

This issue still persists. I have a route that defines a resource that can be of 3 different types, I don't know the type until I resolve getting data from the db and then I can select which is the correct view and controller.

Is this planned for fixing?