PDA Inference Fails with Seeds Outside of Scope

[callensm]

In the current pda-derivation test case, the IDL is properly populated with the PDA seeds since the seeds are declared and referenced within the same module/scope as the Accounts structs.

If you move the seeds outside of the scope of the struct:

mod seeds {
    #[constant]
    pub const MY_SEED: &[u8] = b"my_pda_seed";
}

#[derive(Accounts)]
pub struct Init<'info> {
    #[account(
        seeds = [
            seeds::MY_SEED,
            // ...
        ],
        bump,
        // ...
    )]
    pub my_pda: Account<'info, X>,

    // ...
}

This will fail to parse and translate the seeds into the IDL with:

WARNING: unexpected seed: Path(ExprPath { attrs: [], qself: None, path: Path { leading_colon: None, segments: [PathSegment { ident: Ident(seeds), arguments: None }, Colon2, PathSegment { ident: Ident(MY_SEED), arguments: None }] } })

...and if you use the seed into the module (use seeds::MY_SEED) and remove the module scope prefix, it will still fail with the appropriately modified ident parsing error.

It seems that only seeds defined within the same scope at the Accounts struct that is using them will parse correctly.

[GuidoDipietro]

This is especially annoying if you use some external constant from a common program such as mpl_token_metadata, it can generate many many warnings.

[DevMilk]

I thought same way to write seeds and got same error. It is not possible for now i guess.

[AnderUstarroz]

This really needs a review, aiming for a more flexible way to generate seeds without breaking IDL or generating the mentioned annoying warnings.

[acheroncrypto]

Fixed by #2824.