Tuple input value is not parsed in "Write Contract"

[vbaranov]

Description

Link to the page

https://eth-sepolia.blockscout.com/address/0x0174b6E70b51C739ADb0D6d6c50eA49789FB5028?tab=write_contract

Steps to reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

App version

v1.20.0

Browser

No response

Operating system

None

Additional information

No response

[tom2drum]

will be fixed as part of #1035

[jaymod]

This issue is still present for nested tuples in builds after PR 1413.

Repro:

1. Navigate to https://eth-sepolia.blockscout.com/address/0xc7F957c37193648D087E691016De9542273Be164?tab=contact_code but using a build containing the PR 1413 fix such as https://github.com/blockscout/frontend/pkgs/container/frontend/164130158.
2. Note that the contract contains nested structs (tuples) in the input parameter to the updateFields function.
3. With the changes from PR 1413, the top-level tuple fields are split into their own form fields which works great. Unfortunately, the nested tuple fields are not expanded and still suffer from the same input validation issue as is captured in this ticket.

Taking a look at the original input validation ticket (#1035), arrays are noted as being nestable but the requirement is missing for tuples.

[tom2drum]

Hi @jaymod. You're right, we don't support nested fields since it wasn't part of the initial task. However, we've implemented client-side validation for simple values, which should cover most use cases. For the nested structure, you can pass it as a string representation and the underlying library (viem) will handle the parsing.

[jaymod]

Thanks for the quick reply! Entering a string representation for nested structs works for our use case, but what is the expected format? I tried several variations and always received a Error: Cannot convert undefined to a Bigint error. I also could not find any details about the expected format in the documentation. Are you able to successfully write the nested field in the above contract?

[tom2drum]

Oh, yeah, there is a bug actually, causing it to malfunction currently. I have opened a new issue for it at #1512.

[jaymod]

Awesome thanks! That's what we're seeing as well.