As long as you’re not doing anything weird (such as putting providers on the decorators of your Components or in submodules), Angular DI makes it so that any time anybody asks for a AuthService, they’ll get the same one. So you can use the pattern described in this post to propagate changes in authentication status anywhere in your app that go beyond just “user is logged in or not” to include strongly-typed information such as a user profile.
1 Like