Add ext_contract macro to FungibleTokenMetadataProvider trait #836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Enables users to import FungibleTokenMetadataProvider for cross-contract calls
austinabell
approved these changes
Jun 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, users building smart contracts can use
ext_ft_coreto make cross-contract calls to Fungible token methods enumerated in NEP-141. However, to make a call to theft_metadatamethod, they have to define their own trait in their smart contract becauseFungibleTokenMetadataProviderdoes not have aext_contractmacro. This PR adds theext_contractmacro to theFungibleTokenMetadataProvidertrait so that users do not have to copy/paste this trait into their code.