feat: return response data #563
Conversation
|
This current approach dumps the entire body, not the extract value. This is inconsistent with the old APIs. It should only output the value. FYI @piotr-roslaniec , this probably needs to reflect the output of the ManifestV2 multi-extractions as well. The approach I took in my other PR is naive. |
|
Okay lets merge in the V2 and then i will rebase and take a look here. |
0xJepsen
force-pushed
the
feat/return_value
branch
from
f2921d0 to
a6402ec
Compare
| let path = manifest.response.body.json_path().clone(); | ||
| let body = serde_json::from_slice(&response.notary_response_body.clone().body.unwrap()).unwrap(); | ||
| let value = get_value_from_json_path(&body, &path); | ||
| let manifest_hash = KeccakHasher::hash(serde_json::to_string(&manifest)?.as_bytes()); |
There was a problem hiding this comment.
@piotr-roslaniec we need to make the hash like this so that the same proof produces the same hash. This is because in the on chain verifier, we shouldn't let users submit duplicate proofs. and we need to enable users to recreate the root hash.
|
Would also be nice to have support for these extractions all the way out to the contract. I created an issue on solidity-verifier for that: pluto/solidity-verifier#4 (comment) |
Pull Request
This is a very small change but very important feature for the user. This change just ensures that the data from the response (that we are proving) is returned to the user.