Closed cecton closed 8 years ago
Good question; perhaps the parse_response
can be left out, if it is not returned. Perhaps this should raise an exception on an unexpected response. The return self
is a common pattern for such methods.
Personally I would remove the parsing. It looks like dead code and a user wouldn't expect the response to be parsed if they can't access it anyway. But it is up to you to decide. I will be happy to create the PR of course 😄
My experience with this issue is that I'm working with Sesame and it fails because the updates on Sesame return a 204 No Content and the fix that handles that issue is in the branch develop. So it's blocking without a good reason to block.
:+1: to removing the #parse_response
call.
Hello,
I'm already sorry if this question is totally irrelevant. I'm don't know Ruby at all but I show the issue to a few Ruby developers and none of them found a solution to it.
Here is the piece of code that is puzzling me in the SPARQL::Client:
As you can see. The result of the request is parsed but it is not stored and I believe it is not accessible to the caller since this method returns self.
Is there some magic somewhere that allows retrieving the parsed result?
Thanks