Wrong value for resolved field path

[cslashm]

In erc7730 json schema, a path field is declared as

"path": {
            "title": "Path",
            "type": "string",
            "description": "A path to the field in the structured data. The path is a JSON path expression that can be used to extract the field value from the structured data."
        },

But when applying resolve command we get a complex path object instead of a simple string.
In the following exemple when resolving tether.json, the path for _to param value should be

  "path" : "_to"

but we get:

          "transfer(address,uint256)": {
              "intent": "Send",
              "fields": [
                  {
                      "path": {
                          "type": "data",
                          "absolute": true,
                          "elements": [
                              {
                                  "type": "field",
                                  "identifier": "_to"
                              }
                          ]
                      },

Did I miss something?

[jnicoulaud-ledger]

Hi 👋 Yes, it is intentional, the resolved form is designed so there is no more string parsing to do. You can see difference between input and resolved form here:

• URLs have been fetched
• Contract addresses have been normalized to lowercase
• References have been inlined
• Constants have been inlined
• Field definitions have been inlined
• Selectors have been converted to 4 bytes form

Output of the resolved form does not comply with the input spec schema, you can get the resolved form schema with erc7730 schema resolved.

So the complex object expresses the same thing as _to (a data path of one element, referencing field _to).

Are you looking to build on ERC-7730 ? Please note it is still under development and we are still doing some breaking changes (it should stabilize soon though).