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
I recommend including the interfaces from the I* contracts directly in the contracts that implement them, rather than having them in separate files.
This would be bad practice in other languages, but I believe that in Cadence it helps with security, by simplifying capability descriptions and discouraging using other implementations of the interfaces.
The text was updated successfully, but these errors were encountered:
rheaplex
changed the title
Include Interfaces In Implementation Contracts
Recommendation: Include Interfaces In Implementation Contracts
Sep 28, 2021
Hi @rheaplex,
Do you mean IPackNFT? We have separated the interface because, IIUC, it should be specified so other issuers can use it in the future to interface with PDS.
From the requirements
Provides a Capability that references the Issuer’s own Pack NFT implementation, to allow for the creation of Pack instances. (The Pack NFT will have a well-defined interface specification.)
Please let me know if I have misunderstood it or it is still ok for now to not provide a contract interface.
I recommend including the interfaces from the
I*
contracts directly in the contracts that implement them, rather than having them in separate files.This would be bad practice in other languages, but I believe that in Cadence it helps with security, by simplifying capability descriptions and discouraging using other implementations of the interfaces.
The text was updated successfully, but these errors were encountered: