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

Improvement: don't parse update response #73

Merged
merged 1 commit into from
Aug 27, 2016
Merged

Improvement: don't parse update response #73

merged 1 commit into from
Aug 27, 2016

Conversation

cecton
Copy link
Contributor

@cecton cecton commented Aug 26, 2016

The result of an update is not accessible to the caller. Therefore,
there is no point of parsing it and it's a risk that the whole call
fails if an error occurs during the parsing.

Fixes #71

The result of an update is not accessible to the caller. Therefore,
there is no point of parsing it and it's a risk that the whole call
fails if an error occurs during the parsing.

Fixes #71
@coveralls
Copy link

coveralls commented Aug 26, 2016

Coverage Status

Coverage remained the same at 94.318% when pulling 3f21267 on cecton:dont-parse-update-response into 9f173a5 on ruby-rdf:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.318% when pulling 3f21267 on cecton:dont-parse-update-response into 9f173a5 on ruby-rdf:develop.

@no-reply no-reply merged commit c2c78a2 into ruby-rdf:develop Aug 27, 2016
@cecton cecton deleted the dont-parse-update-response branch August 29, 2016 10:13
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