This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
Work around bug with empty response bodies #227
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This would close #224 |
cbeer
force-pushed
the
rest-assured-642
branch
from
575cadc
to
829f992
Compare
This was referenced Sep 26, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have an LDP implementation does not add server-managed triples, which triggers a
NullPointerErrorwithin RestAssured (reported upstream as rest-assured/rest-assured#642).Handling the response graph as a string does not cause the same problem. It seems like the graphs in the test suite are sufficiently small that using strings oughtn't cause too many problems.