Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] expected parentheses #369

Open
Will-Smith11 opened this issue Oct 13, 2023 · 1 comment
Open

[Bug] expected parentheses #369

Will-Smith11 opened this issue Oct 13, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Will-Smith11
Copy link
Contributor

Component

sol! macro

What version of Alloy are you on?

No response

Operating System

Linux

Describe the bug

image
https://etherscan.io/address/0x00000000000001ad428e4906ae43d8f9852d0dd6

@Will-Smith11 Will-Smith11 added the bug Something isn't working label Oct 13, 2023
@DaniPopes
Copy link
Member

DaniPopes commented Oct 15, 2023

Might not be related, but it's very weird that the ABI internal types on that contract are enumSide instead of enum Side, or structConsiderationItem, or addresspayable.

Edit: it is related, these are the generated tokens. tuple again being parsed as the tuple type (tuple(uint, address, ...)).

interface Seaport_1_4 {
    type addresspayable is address;
    type enumBasicOrderType is uint8;
    type enumItemType is uint8;
    type enumOrderType is uint8;
    type enumSide is uint8;
    type structAdvancedOrder is tuple;
    type structBasicOrderParameters is tuple;
    type structOrder is tuple;
    type structOrderComponents is tuple;
    type structOrderParameters is tuple;
    type structReceivedItem is tuple;

    // ...
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants