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: Generic structs error in the idl if they're populated with custom structs #3013

Closed
cryptopapi997 opened this issue Jun 8, 2024 · 1 comment · Fixed by #3016
Closed
Labels
bug Something isn't working idl related to the IDL, either program or client side

Comments

@cryptopapi997
Copy link
Contributor

The title says it all - if we do:

#[account]
struct MyAccount {
    data: GStruct<u32>,
}

#[derive(AnchorSerialize, AnchorDeserialize, Clone)]
struct GStruct<T> {
    data: T,
}

the generated idl is fine and can be used. If we do

#[account]
struct MyAccount {
    data: GStruct<MyStruct>,
}

#[derive(AnchorSerialize, AnchorDeserialize, Clone)]
struct GStruct<T> {
    data: T,
}

#[derive(AnchorSerialize, AnchorDeserialize, Clone)]
struct MyStruct {
    data: u32,
}

the generated idl is unparsable. Might open a PR for this later, but in case I forget wanted to at least have the issue. MRE for this here: https://github.com/cryptopapi997/anchor-generics-mre

@acheroncrypto acheroncrypto added bug Something isn't working idl related to the IDL, either program or client side labels Jun 8, 2024
@cryptopapi997
Copy link
Contributor Author

Should be fixed by #3016, feel free to take a look @acheroncrypto

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working idl related to the IDL, either program or client side
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants