Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated $signInWithPopup() and $signInWithRedirect() docs #896

Merged
merged 2 commits into from
Jan 12, 2017

Conversation

jwngr
Copy link

@jwngr jwngr commented Jan 3, 2017

Description

Clarifies and adds additional examples to the reference docs for $signInWithPopup() and $signInWithRedirect().

Closes #894.

Code sample

N/A

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.0% when pulling 3814b8a on jw-signin-docs-fixes into c22ef72 on master.

Copy link
Contributor

@katowulf katowulf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Two little nitpicks to consider. I'll mark this lgtm as I'm not sure they're actionable.

Authenticates the client using a credential (potentially created from OAuth Tokens). This function takes one
arguments: the credential object. This may be obtained from individual auth providers under `firebase.auth()`;
Authenticates the client using a credential (potentially created from OAuth tokens). This function
takes a single argument: the credential object. This may be obtained from individual auth providers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence doesn't really help me understand how to create a credential object and I think it's going to be easy to miss that firebase.auth() refers to the underlying SDK.

Sadly, there doesn't seem to be a good example in the auth guide or the api reference to help clear this up. So maybe ignore unless you have ideas.

@@ -750,7 +787,7 @@ This method returns a promise which is resolved or rejected when the authenticat
completed. If successful, the promise will be fulfilled with an object containing authentication
data about the signed-in user. If unsuccessful, the promise will be rejected with an `Error` object.

Firebase currently supports Facebook, GitHub, Google, and Twitter authentication. Refer to
Firebase currently supports Facebook, GitHub, Google, and Twitter authentication. Refer to the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Firebase currently supports Facebook, GitHub, Google, and Twitter identity providers for use with $signInWithCredential. (We support other authentication methods: email/password, anonymous, and custom)

@katowulf katowulf assigned jwngr and unassigned katowulf Jan 11, 2017
@jwngr jwngr assigned katowulf and unassigned jwngr Jan 12, 2017
@coveralls
Copy link

Coverage Status

Coverage increased (+3.7%) to 93.716% when pulling 88c2909 on jw-signin-docs-fixes into c22ef72 on master.

@katowulf
Copy link
Contributor

lgtm ☃

@katowulf katowulf assigned jwngr and unassigned katowulf Jan 12, 2017
@jwngr jwngr merged commit 94ca5bc into master Jan 12, 2017
@jwngr jwngr deleted the jw-signin-docs-fixes branch January 12, 2017 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants