Skip to content

Document Async Current User (JS) #496

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

Merged
merged 1 commit into from
Jan 15, 2018
Merged

Document Async Current User (JS) #496

merged 1 commit into from
Jan 15, 2018

Conversation

montymxb
Copy link
Contributor

@montymxb montymxb commented Jan 15, 2018

Adds a small note in the documentation regarding usage of currentAsync() when storage is asynchronous. This is noted lack of documentation in issue #500.

What still stands is whether we should suggest usage of currentAsync or currentUserAsync. Since it seems the former was used to resolve the issue mentioned above I have chosen that for an addition the docs.

Adds a small note in the documentation regarding usage of `currentAsync()` when storage is asynchronous. This is noted lack of documentation in issue #500. 

What still stands is whether we should suggest usage of `currentAsync` or `currentUserAsync`. Since it seems the former was used to resolve the issue mentioned above I have chosen that for an additition the docs.
@montymxb montymxb merged commit 0a80fd9 into gh-pages Jan 15, 2018
@montymxb montymxb deleted the montymxb-patch-1 branch January 15, 2018 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants