Skip to content

Conversation

@jhansche
Copy link
Contributor

@jhansche jhansche commented Jan 6, 2017

Joe Hansche added 4 commits January 6, 2017 13:11
This allows the results to be chained together via tasks, and also allows the
CurrentUserController to be overridden to provide additional functionality
for retrieving the session token.

This matches how the ParseCloud and ParseObject retrieve the session token.
@jhansche
Copy link
Contributor Author

jhansche commented Feb 3, 2017

Today's commits add unit tests, and switch to getCurrentSessionTokenAsync(), to match how other authenticated calls are made in Parse core.

JSONObject jsonObject = new JSONObject();
jsonObject.put("op", "subscribe");
jsonObject.put("requestId", requestId);
if (sessionToken != null) jsonObject.put("sessionToken", sessionToken);
Copy link
Contributor

Choose a reason for hiding this comment

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

In ConnectClientOperation we always the sessionToken, even if it's null.
Should we add the null check also in ConnectClientOperation?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think the null check is required. The field itself is optional anyway. I just didn't pay attention to the way ConnectClientOperation did it.

I'd be fine with removing the null check if we want them to be consistent.

@mmimeault
Copy link
Contributor

Otherwise it look pretty good.

@mmimeault
Copy link
Contributor

awesome +1

@mmimeault mmimeault merged commit d055f35 into parse-community:tasks/initial-project Feb 22, 2017
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.

2 participants