Add a Generic type for Meta object

[Reblixt]

Consider how to add a generic type on the Meta object so it does not conflict with the NFT object.

Pros:

• This is for increasing flexibility for the Collection creator on what to store in the NFT and so they do not need to create a Wrapper object.

Cons:

• Could increase the complexity of a funciton calls

Resources:
use std::type_name::TypeName;
or
public struct Collection<T: store, meta: key + store> has key, store {...}
or some other solution

[tomcrown]

Refactor Proposal: Split Metadata Generics

Problem

Right now both Collectible<T> and Attribute<T> use a single generic type T for metadata:

• Attribute<T> has meta: Option<T>
• Collectible<T> has meta: Option<T>

This creates a conflict when building collections:

• If the Collection<T> is defined with one T, then both attributes and collectibles are forced to share the same metadata type.
• That’s limiting, since attribute-level metadata and NFT-level metadata often serve different purposes.

Example of the Problem

• A collectible might want metadata = ArtistInfo { creator, mint_time }.
• An attribute might want metadata = TraitRarity { rarity_pct, category }.
• Today, you’d need to force both to share one type or wrap them manually, which is clunky.

Proposed Refactor

Introduce two generic parameters:

public struct Collectible<AttrMeta: store, NftMeta: store + key> has key, store {...}

And update Collection:

public struct Collection<AttrMeta: store, NftMeta: store + key> has key, store {...}

Meanwhile, Attribute<T> remains unchanged:

public struct Attribute<T: store> has store {...}

Benefits

• Clear separation between attribute metadata and collectible metadata.
• More flexibility for collection creators without wrapper types.
• Works naturally with different use cases (e.g., game NFTs vs art NFTs).

Costs

• Function signatures will now need two generics:

public fun mint<AttrMeta: store, NftMeta: store + key>(...): Collectible<AttrMeta, NftMeta> { ... }

• Slightly more verbose function calls.

Contribution Plan

1. Update Collectible and Collection to accept two generic params.
2. Refactor all related functions (mint) to carry both generics.
3. Keep Attribute<T> as is.

This strikes a balance between flexibility for creators and manageable complexity for developers.

[Reblixt]

Hey @tomcrown, Thank you for wanting to contribute to this Dynamic NFT Framework!

This is something i had in my mind! :D

Please go ahead,

Thanks!