Is your enhancement request related to a problem? Please describe.
Sometimes I need to use 1+ ix in the uses field. In the TokenProg ixs it is very common to find inputs with the same name (i.e. authority). Because the generator infers that two inputs of a method have the same name and type ARE the same input, it is not possible to pass different args to different cpi ixs with inputs of the same name in the context of a method call.
But this is even more confusing because Codigo renamed many of these inputs, not following nor Anchor nor Native SPL interfaces, making very confusing to understand the meaning of owner in the context of several ixs that requires an authority in their original names, like in:
uses:
- csl_spl_token.initialize_mint2
- csl_spl_assoc_token.create
- csl_spl_token.mint_to
- csl_spl_token.set_authority
Describe the solution you'd like
To not infer that it is the same input, and to follow either Native or Anchor naming for SPL programs inputs
Is your enhancement request related to a problem? Please describe.
Sometimes I need to use 1+ ix in the
usesfield. In the TokenProg ixs it is very common to find inputs with the same name (i.e.authority). Because the generator infers that two inputs of a method have the same name and type ARE the same input, it is not possible to pass different args to different cpi ixs with inputs of the same name in the context of a method call.But this is even more confusing because Codigo renamed many of these inputs, not following nor Anchor nor Native SPL interfaces, making very confusing to understand the meaning of
ownerin the context of several ixs that requires an authority in their original names, like in:Describe the solution you'd like
To not infer that it is the same input, and to follow either Native or Anchor naming for SPL programs inputs