Wrong value for resolved field path
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
The issue names the ERC-7730 JSON schema, the resolve command, and tether.json, but no repository files or tests. Start by tracing how resolve builds the field path object and compare it with the schema's string declaration and the expected _to output. Done means the resolved path follows the declared schema and the tether.json example produces the expected representation.
Written by the indexing model from the issue text.
Description
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?
- Dominant language
- Python
- Stars
- 1
- Forks
- 13
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LedgerHQ/python-erc7730
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
LedgerHQ/python-erc7730#338 · 1 comment ·
Maintainers usually reply within 2 days
All issues in LedgerHQ/python-erc7730
Similar issues
-
#bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
apache/superset#44923 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lawndoc/stack-back#123 ·
-
Add: EntuneOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AbdelStark/awesome-typesafe-jev#187 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
repowise-dev/repowise#2966 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days