Add assertions to generic transfer and update docs #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #162
Description
generic_transfer_with_address
to make sure the vault is the correct typeMaliciousToken
to test the transaction.MaliciousToken
is the same asExampleToken
, but returns theExampleToken
paths in theFTVaultData
view instead of its own paths.FungibleToken
I can't think of any other assertions to put in the transactions, but I am open to suggestions
For contributor use:
master
branchFiles changed
in the Github PR explorer