This repository was archived by the owner on Apr 4, 2023. It is now read-only.
Storing additional user info as local state #919
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Interesting approach, thank you! |
|
Added a similar implementation for iOS. Will be available in 7.1.0 (released later this week). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Eddy, since I didn't have any news from your side, I tryed to solve the problem my way :)
As stated in #903, additionalUserInfo are not retrieved when calling getCurrentUser using nativeAPI.
So in this approach I try to mimick what is being done for the web api, that is, storing the additional info as a global object and returning it when asked for.
Android only.