Add support for dynamic and nested NFTs #36
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.
NftType enumto differentiate betweenstatic,dynamic, andnestedNFTs. The NftData struct contains the new fields nftType, parentId, and childIds to support dynamic and nested NFTs.createStaticNftfunction creates a new static NFT with the specified recipient and token ID.createDynamicNftfunction creates a new dynamic NFT with a new token ID and the specified recipient.createNestedNftfunction creates a new nested NFT with a new token ID, the specified recipient, and the parent NFT ID. It also adds the child NFT ID to thechildIdsarray of the parent NFT.getChildNftsfunction returns an array of child NFT IDs for a given parent NFT ID. (used to retrieve child NFTs for the nested NFTs)