Skip to content

Properly handle null query response #425

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Dec 4, 2018
Merged

Properly handle null query response #425

merged 1 commit into from
Dec 4, 2018

Conversation

dplewis
Copy link
Member

@dplewis dplewis commented Dec 4, 2018

superced #388

@codecov
Copy link

codecov bot commented Dec 4, 2018 •
edited
Loading

Codecov Report

Merging #425 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #425   +/-   ##
=======================================
  Coverage   98.98%   98.98%           
=======================================
  Files          38       38           
  Lines        3150     3150           
=======================================
  Hits         3118     3118           
  Misses         32       32
Impacted Files Coverage Δ
src/Parse/ParseQuery.php 99.47% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bef9085...d549b8f. Read the comment docs.

@dplewis dplewis requested a review from flovilmart December 4, 2018 03:31
@dplewis dplewis merged commit 8efe533 into parse-community:master Dec 4, 2018
@dplewis dplewis deleted the handle-null-response branch December 4, 2018 17:02
@dplewis dplewis mentioned this pull request Dec 4, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@flovilmart flovilmart flovilmart approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dplewis @flovilmart