Francis Galiegue
Francis Galiegue
I have to agree with that. Since my current job has led me to experience such problems, the two solutions would be to: - either get rid of Guava entirely,...
Hello, I will need to reread the spec, it's been some time. For answers you seem to require `error`, that doesn't look right...
Hmm OK, I have reread the spec but I cannot see the part where it says that there should not be more keys than the ones defined? URL used: http://www.jsonrpc.org/specification
See commit above. The changes are in fact rather simple: - we move the `required` properties out of `common` and into each of `result` and `error`; - we add `additionalProperties`...
> The spec says "The Response is expressed as a single JSON Object, with the following members:" which I read as saying that those and only those members are allowed...
OK, can you review the commit above? If you agree with the commit message, I'll rebase onto master and push it.
Hmm, what are the error messages? There are also error messages with my own validator here even though I cannot figure out why they are happening...
Uh, OK, I know what is happening. It is because of `additionalProperties`. One thing to remember here is that schemas are _not_ merged. As a result, `additionalProperties` depends on what...
Confirmed: this works. I'll post an update to the patch soon.
OK, can you try with this updated schema?