Skip to content

JSON serialization of ExecTxResult breaks naming of fields as they were in ResponseDeliverTx #855

@mzabaluev

Description

@mzabaluev

tendermint/tendermint#9468 introduced the ExecTxResult message type as a drop-in replacement for ResponseDeliverTx where it was used inside other messages. However, it did not carry over the options that explicitly set names for some of the fields:

  int64          gas_wanted = 5 [json_name = "gas_wanted"];
  int64          gas_used   = 6 [json_name = "gas_used"];

As a result, the JSON serialization of the structures containing ExecTxResult in RPC has changed in a backward-incompatible way.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingrpc

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions