Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add better, more flexible APIs for SDK initialization. #79

Merged
merged 1 commit into from
Dec 14, 2015

Conversation

richardjrossiii
Copy link
Contributor

This PR includes public API changes

Proposing a new initialization API, to allow for more flexibility and clarity in the future:

ParseClient.Initialize(new ParseClient.Configuration {
    ApplicationId = ...,
    WindowsKey = ...
});

No APIs are being directly deprecated at this time, only additions for the time being.


This PR hopes to unify some of these initialization settings int o a single 'configuration' class that can be easily used to intialize parse in a much cleaner way, especially as we add even more initialization options.

Depends on #77.

@richardjrossiii richardjrossiii force-pushed the richardross.initialization.update branch from a53d631 to 36895ba Compare November 16, 2015 23:24
@richardjrossiii richardjrossiii changed the title Richardross.initialization.update Add better, more flexible APIs for SDK initialization. Nov 16, 2015
@richardjrossiii richardjrossiii force-pushed the richardross.initialization.update branch from 36895ba to c39e232 Compare November 16, 2015 23:36
@richardjrossiii richardjrossiii force-pushed the richardross.initialization.update branch from c39e232 to f11d216 Compare December 9, 2015 23:01
@@ -71,11 +72,6 @@ internal class ParseCommand : HttpRequest {
if (!string.IsNullOrEmpty(ParseClient.PlatformHooks.OSVersion)) {
Headers.Add(new KeyValuePair<string, string>("X-Parse-OS-Version", ParseClient.PlatformHooks.OSVersion));
}
if (!string.IsNullOrEmpty(ParseClient.MasterKey)) {
Copy link
Contributor

Choose a reason for hiding this comment

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

this was here for a reason, IIRC for Cloud Code stuff. Have you verified that IntegrationTest still run?

@hallucinogen
Copy link
Contributor

Looking good. Would be good if you can add a test (something like "ParseCommand will return correct header after I call ParseClient.Initialize(someConfiguration)")

This PR hopes to unify some of these initialization settings int o a single 'configuration' class that can be easily used to intialize parse in a much cleaner way, especially as we add even more initialization options.

Depends on #77.
@richardjrossiii richardjrossiii force-pushed the richardross.initialization.update branch from f11d216 to 8f45eb2 Compare December 14, 2015 18:34
richardjrossiii added a commit that referenced this pull request Dec 14, 2015
…update

Add better, more flexible APIs for SDK initialization.
@richardjrossiii richardjrossiii merged commit a4fa591 into master Dec 14, 2015
@richardjrossiii richardjrossiii deleted the richardross.initialization.update branch December 14, 2015 18:38
@richardjrossiii richardjrossiii added this to the 1.7.0 milestone Jan 8, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants