Generally I don't think we need to do hardcore mega-reactivity stuff where you avoid storing state on classes at all costs, but in the case of the local user service, using async pipes better to avoid storing stuff like isLoggedIn everywhere makes a lot of sense.
Just a couple small things.
Generally I don't think we need to do hardcore mega-reactivity stuff where you avoid storing state on classes at all costs, but in the case of the local user service, using async pipes better to avoid storing stuff like
isLoggedIneverywhere makes a lot of sense.