Is your enhancement request related to a problem? Please describe.
When using the method csl_spl_account_compression.init_empty_merkle_tree it will generate the following call in my stub:
csl_spl_account_compression::src::cpi::init_empty_merkle_tree(
for_init_empty_merkle_tree,
30,
512,
)?;
Describe the solution you'd like
I'd like the generator to put the values for max depth and buffer, in this case, 30 and 512 respectively within the init_empty_merkle_tree itself. These values cannot be changed because they can break other parts of the code. I wouldn't like another colleague or me to change these values. These values' source of truth must be the CIDL, specifically the capacity attribute.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your enhancement request related to a problem? Please describe.
When using the method
csl_spl_account_compression.init_empty_merkle_treeit will generate the following call in my stub:Describe the solution you'd like
I'd like the generator to put the values for max depth and buffer, in this case, 30 and 512 respectively within the
init_empty_merkle_treeitself. These values cannot be changed because they can break other parts of the code. I wouldn't like another colleague or me to change these values. These values' source of truth must be the CIDL, specifically the capacity attribute.Describe alternatives you've considered
N/A
Additional context
N/A