Skip to content
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

Migrate ParseGlobalConfig to new database storage API. #901

Merged
merged 2 commits into from Mar 7, 2016

Conversation

nlutsenko
Copy link
Contributor

Also fix the thing, so it properly upserts if config does not exist.
This is modeled close to how parse.com works.

@drew-gross
Copy link
Contributor

Sweet! Have you tried this with the dashboard?

@codecov-io
Copy link

Current coverage is 91.73%

Merging #901 into master will increase coverage by +0.05% as of b1cb0e8

@@            master    #901   diff @@
======================================
  Files           71      71       
  Stmts         4102    4103     +1
  Branches       850     851     +1
  Methods          0       0       
======================================
+ Hit           3761    3764     +3
  Partial         10      10       
+ Missed         331     329     -2

Review entire Coverage Diff as of b1cb0e8

Powered by Codecov. Updated on successful CI builds.

@nlutsenko
Copy link
Contributor Author

Nope, not yet, can do, but probably a bit later...

nlutsenko added a commit that referenced this pull request Mar 7, 2016
Migrate ParseGlobalConfig to new database storage API.
@nlutsenko nlutsenko merged commit 477e978 into master Mar 7, 2016
@nlutsenko nlutsenko deleted the nlutsenko.config branch March 7, 2016 22:50
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.

None yet

4 participants