I have a UI Router defined something like this (trimmed for simplicity):
$stateProvider
.state(\'someState\', {
resolve: {
You should review the angular docs on dependency injection:
So each type of angular component has its own list of acceptable components to inject. Since services are singletons, it really wouldn't make any sense to inject a value as part of a resolve. If you had two separate places on your page that used a service with different resolves, the outcome would be indeterminate. It would make no more sense than injecting $scope
into your service. It makes sense for controllers because the controller is responsible for the same area of the page that is being resolved.
If your someService
needs to use the data in model, it should have a function that takes the data as a parameter and your controller should pass it.