scope.apply with shared services about angular-widget HOT 4 CLOSED

Yeah, shared services need $apply explicitly in order to trigger digest. I do supply an helper for you if the shared service has methods that are actually setters, that's what the second argument to widgetsProvider.addServiceToShare is for. If you are sharing $http, this second argument won't help you much because you need the digest to be triggered after the promise resolves... It is very easy to solve though... But can you describe the reason you need to share $http and not have each widget/micro-app use his own $http?

from angular-widget.

The $http service is intercepted ($httpProvider.interceptors.push('...');) to add an authentication-token header and handle API responses like 401 Unauthorised (display login form) in a generic way.

I found no way to share providers – although that might be a nice feature as well, if thats even possible? I guess in angular-widget there could be a widgetsProvider.addProviderToShare method which shares a provider using something like $provide.provider(name, provider). Do you think this makes sense at all?

Maybe I'll introduce a ui-router state for each widget with a resolve 'function' which supplies data to the controller, then it should work without a $scope.$apply.

from angular-widget.

In the manifest generator you can pass an extra config block to the micro
app. Why not add the interceptor with this argument and so you'll have
separate services, each with its own interceptor?
On Oct 23, 2014 8:27 PM, "Adrian Philipp" [email protected] wrote:

The $http service is intercepted ($httpProvider.interceptors.push('...');)
to add an authentication-token header and handle API responses like401
Unauthorised` (display login form) in a generic way. I found no way to
share providers – although that might be a nice feature as well, if thats
even possible.

Maybe I'll introduce a ui-router state for each widget with a resolve
'function' which supplies data to the controller, then it should work
without a $scope.$apply.

—
Reply to this email directly or view it on GitHub
#4 (comment).

from angular-widget.

Hey Shahar, thank you very much!

from angular-widget.