You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Related to the bug already documented in #26 , when trying to use a csl_token.mint_to in Anchor, the generator infers that I want to pass an ATA, so the client generates a PDA check for the address (Although I'm trying to use a regular TokenAccount).
Nevertheless, the PDA check uses a call to deriveCslSplTokenAccount() that is not defined. To Reproduce
- name: mint_to
uses:
- csl_spl_token.mint_to
Expected behavior
To define the fn if needed.
Platform version:
CLI Version [e.g. v0.1.0]
GenService Version v0.8
Extension (mark with an X the extension):
Solana Native [ ]
Solana Anchor [x]
The text was updated successfully, but these errors were encountered:
When trying to use a csl_token.mint_to in Anchor, the generator infers that I want to pass an ATA, so the client generates a PDA check for the address. However, I'm trying to use a regular TokenAccount.
Nevertheless, if I wanted to use an ata, the PDA check uses a call to deriveCslSplTokenAccount() that is not defined.
This is a bug
Please close this ticket and create a new one to report the bug of undefined deriveCslSplTokenAccount, or, modify this ticket to only reflect that bug undefined deriveCslSplTokenAccount.
julianzamt
changed the title
deriveCslSplTokenAccount not requested, but nor imported.
undefined deriveCslSplTokenAccount
Oct 23, 2023
Describe the bug
Related to the bug already documented in #26 , when trying to use a csl_token.mint_to in Anchor, the generator infers that I want to pass an ATA, so the client generates a PDA check for the address (Although I'm trying to use a regular TokenAccount).
Nevertheless, the PDA check uses a call to deriveCslSplTokenAccount() that is not defined.
To Reproduce
Expected behavior
To define the fn if needed.
Platform version:
Extension (mark with an X the extension):
The text was updated successfully, but these errors were encountered: