Skip to content

Fixed 'IsPushEnabled' handling in update RC client API call #2542

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 3 commits into from
Oct 9, 2017

Conversation

agafox
Copy link
Contributor

@agafox agafox commented Oct 3, 2017

No description provided.

@agafox agafox requested review from gvagenas and removed request for gvagenas October 3, 2017 12:55
@maria-farooq
Copy link

would it make sense to add a test case similar to what Antonis mentioned failing in original issue #2503

if (getBoolean("IsPushEnabled", data)) {
result = result.setPushClientIdentity(client.getSid().toString());
} else {
result = result.setPushClientIdentity(null);
Copy link
Contributor

Choose a reason for hiding this comment

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

i guess this is the only meaningfull change of this PR. This method is strange, it receives a final Client not meant to be modified. Then we assigned to a new var without final, and then we returned the modified instance... not sure what is the reason for this, i know is not part of this PR. Wouldnt make more sense to declare argument as regular non final,rather than suggesting Client is not modified to be modified later...?

@jaimecasero
Copy link
Contributor

mostly ok to be merged...

@agafox agafox merged commit 4f87d46 into master Oct 9, 2017
@jaimecasero jaimecasero deleted the Issue-2503 branch April 11, 2018 20:12
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