Closed redbassett closed 7 years ago
Hi any updates on my feedback?
Sorry, I've been away from this issue for a while (and will be for a while longer). I also haven't had time to look into the google-signin
element yet, however I'm all for consistency between the sign-in process for the two.
Ah, np. It was just a suggestion on naming. I think we're pretty close on this!
Thanks for pointing me to this one. It is spot on to what I desire! The name login-attempt also makes sense to me, since it has been nothing more than an attempt.
Yeah, the names here were originally going to be based off of the Firebase JS API, however the process of using a Polymer element is already different enough that switching to the naming convention used by another similar element makes sense.
The
firebase-auth
element provides events foron-login
,on-error
, andon-logout
, however there is no event fired when Firebase confirms the lack of a logged in user. This pull request adds such an event (tentatively calledauthenticated
), which is fired any time theref
's authentication state changes (due to the callback provided toref.onAuth
). This can also be thought of as being called wheneverstatusKnown
is set to true.To use the
authenticated
event, simply add anon-authenticated
argument to thefirebase-auth
element with a value representing the name of the method to call. Note that this method will be called every time the authentication state changes (including logins, logouts, and page reloads).