Skip to content

inconsistency in handling redefined types #10

@cc32d9

Description

@cc32d9

On mainnet, mydex1engine has ABI that redefines some standard types:

    },{
      "name": "extended_symbol",
      "base": "",
      "fields": [{
          "name": "sym",
          "type": "symbol"
        },{
          "name": "contract",
          "type": "account_name"
        }
      ]
    },{
      "name": "extended_asset",
      "base": "",
      "fields": [{
          "name": "quantity",
          "type": "asset"
        },{
          "name": "contract",
          "type": "account_name"
        }
      ]
    }

when parsing the binary output from state history plugin, abieos throws an exception:

error: abi redefines type "extended_asset"

So, it needs to be more consistent: either nodeos should reject uploading of such an ABI, or abieos should tolerate and work around this error. Probably both should be done, as this wrong ABI is already carved in history.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions