You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This library is already almost 2 years old. There is a lot of people who come to this as an easy way out to set up firebase authentication in react applications since it aims to be very straightforward, and I'd say it achieves the goal well.
Yet, I'm not completely happy with the current Higher Order Function design, and I feel like the current API offering static implementations of authentication methods creates a sort of vendor lock-in to this library, which I don't appreciate and feel like we could offer something more flexible instead.
Proposal
First: a Hooks based API.
Most folks that come to use this library want to just have it managing the state regarding firebase authentication and ease to just hook firebase.auth() into a component and have methods ready to go.
The very same experience could be given through a useFirebaseAuth() hook.
(more details to come)
The text was updated successfully, but these errors were encountered:
Context
This library is already almost 2 years old. There is a lot of people who come to this as an easy way out to set up firebase authentication in react applications since it aims to be very straightforward, and I'd say it achieves the goal well.
Yet, I'm not completely happy with the current Higher Order Function design, and I feel like the current API offering static implementations of authentication methods creates a sort of vendor lock-in to this library, which I don't appreciate and feel like we could offer something more flexible instead.
Proposal
First: a Hooks based API.
Most folks that come to use this library want to just have it managing the state regarding firebase authentication and ease to just hook
firebase.auth()
into a component and have methods ready to go.The very same experience could be given through a
useFirebaseAuth()
hook.(more details to come)
The text was updated successfully, but these errors were encountered: