broadcast userInfo (_oauthInfo) instead of setting it on rootscope about azure-activedirectory-library-for-js

[omercs]

We added userinfo to rootscope to reduce amount of coding required for developers. We want developers to start with minimum changes.

[ThorstenHans]

yes, but having some data being populated within the rootscope from a dependent library isn't a good thing. I don't like the fact that a Service is manipulating my rootscope..

[RobARichardson]

+1

[tedvanderveen]

+1

[tushargupta51]

Setting things on rootScope is similar to setting things to window object. We added userInfo to rootScope to make it easier for developers to access the logged in user. I agree that it is not the best practice to modify things globally or on global scope. Closing this issue as unfortunately we cannot change this now, as this will be a breaking change. We will consider the feedback for our next generation of adal library (we are actively working on that right now).