yes, it is, because we need to set the user value from the firebase auth observer. We can however keep that one readonly and private and create a computed from it to expose it to the outside - that way the signal is not changed from the outside...
Well, the issues are basically in compatibility with different Angular versions. So at the installation stage - and it can be really frustrating. E.g. in v16, I had to have exact versions of angular fire and rxfire to get it working (I was creating a course on Authentication back then). Second is angular fire now basically just re exports the same firebase js SDK modular functions - so the need for it has become less.
Thanks for this one
Welcome 🙂
Great tutorial
Great tutorial. Can you create one for Google sign in using redirection.
Good suggestion! I'll add it to my list :)
great video, i have a simple question, object user in service authenticator, is it a writable signal?
yes, it is, because we need to set the user value from the firebase auth observer. We can however keep that one readonly and private and create a computed from it to expose it to the outside - that way the signal is not changed from the outside...
@ZoaibKhan that's what i think, why expose user signal and anyone could be write on it
Nice sir make a video for role based auth and menu restriction
Yeah, that's a great suggestion. I have something in mind :)
Can you explain what issues there are currently with angularfire?
Well, the issues are basically in compatibility with different Angular versions. So at the installation stage - and it can be really frustrating. E.g. in v16, I had to have exact versions of angular fire and rxfire to get it working (I was creating a course on Authentication back then).
Second is angular fire now basically just re exports the same firebase js SDK modular functions - so the need for it has become less.