Skip to content

Avoid cleaning currentUser authData in setState #304

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
Dec 17, 2015

Conversation

wangmengyan95
Copy link
Contributor

Fixes #269

@facebook-github-bot
Copy link

By analyzing the blame information on this pull request, we identified @grantland and @hallucinogen to be potential reviewers.

}
// Avoid clearing authData when updating the current user's State via ParseQuery result
if (isCurrentUser() && getAuthData() != null && newState.get(KEY_AUTH_DATA) == null) {
newState = newState.newBuilder().put(KEY_AUTH_DATA, getAuthData()).build();
Copy link
Contributor

Choose a reason for hiding this comment

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

Nit: Let's move isCurrentUser() check out a level so we don't have to do it twice

@grantland
Copy link
Contributor

One nit, otherwise LGTM

@wangmengyan95 wangmengyan95 force-pushed the wangmengyan.fix_clear_currentUser_authData branch from df0a95d to 4971873 Compare December 17, 2015 02:44
@facebook-github-bot
Copy link

@wangmengyan95 updated the pull request.

wangmengyan95 added a commit that referenced this pull request Dec 17, 2015
…entUser_authData

Avoid cleaning currentUser authData in setState
@wangmengyan95 wangmengyan95 merged commit 00e0d08 into master Dec 17, 2015
@wangmengyan95 wangmengyan95 deleted the wangmengyan.fix_clear_currentUser_authData branch December 17, 2015 02:53
@grantland grantland modified the milestone: 1.11.1 Dec 17, 2015
@facebook-github-bot
Copy link

@wangmengyan95 updated the pull request.

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.

3 participants