feat(story-nft): implement IP metadata setting during mint #113
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.
Description
This PR introduces the ability to set IP metadata during the minting process for
OrgNFT
andBaseStoryNFT
. It ensures that when a new IP is registered, its metadata is provided by the user and set throughCoreMetadataModule
.Key Changes
_mintAndRegisterIp
function in bothBaseStoryNFT
andOrgNFT
.StorageBadgeNFT
for storing IP metadata, which will be initialized during deployment. The same metadata will be the same across all badges in the collection.OrgNFT
to accept theIPMetadata
struct defined inWorkflowStructs
.OrgStoryNFTFactory
deployment functions to accept theIPMetadata
struct and pass it during the minting ofOrgNFTs
.Test Plan
Added calls to
assertMetadata
to verify that IP metadata is correctly set for IPs minted fromOrgNFT
andStoryBadgeNFT
. All existing tests pass locally.