Skip to content

Allow custom server URLs to be set and used via ParseClient.Configuration. #147

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 6, 2016

Conversation

richardjrossiii
Copy link
Contributor

No description provided.

@@ -122,7 +129,7 @@ public struct Configuration {
/// </param>
public static void Initialize(Configuration configuration) {
lock (mutex) {
HostName = HostName ?? new Uri("https://api.parse.com/1/");
Copy link
Contributor

Choose a reason for hiding this comment

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

do we still HostName? (even in tests). If we don't, we need to clean that up (doesn't need to be in this PR) since it's source of confusion (i.e. which one should I use, HostName or CurrentConfiguration.Server?)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You're right. I can update all of our internal tests to use Configuration.Server.

@hallucinogen
Copy link
Contributor

lgtmcorgi

Don't forget to update IntegrationTests

EDIT: plz update UnitTests

@richardjrossiii
Copy link
Contributor Author

UnitTests now pass.

@hallucinogen
Copy link
Contributor

LGTM

richardjrossiii added a commit that referenced this pull request Jan 6, 2016
…iguration

Allow custom server URLs to be set and used via ParseClient.Configuration.
@richardjrossiii richardjrossiii merged commit 7458e03 into master Jan 6, 2016
@richardjrossiii richardjrossiii deleted the richardross.serverurl.configuration branch January 6, 2016 23:59
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