Closed ryo-casper closed 2 months ago
Hi @ryo-casper
I'm looking at how we handled info_get_deploy
in 1.x node and how we return it in sidecar for 2.0
Those are two different structures. The old one had a collection of execution results, the new one has one optional. The json schema actually allows all three:
"execution_result": <value>
"execution_result": null
execution_result
field at all
I'm not sure what the problem here is exactly, please explain. You expect the response value to be exactly the same as the 1.x one?Please keep only those cases
"execution_result": value "execution_result": null
and remove this
no execution_result field at all
execution_result
type is incorrect in theinfo_get_deploy
RPC method. Current type:null
Actual type: undefinedhttps://github.com/casper-network/casper-sidecar/blob/016a0f2c2dbf1f3dab75ac58f8d130035e6a7c97/rpc_sidecar/src/rpcs/info.rs#L130-L131
Please check all the fields where serialization is skipped especially for
Option<T>
, they should beundefined
in the schema.