Refactoring

[Reblixt]

• To much logic is stored in the collectible.move file.

• See if we could refactor out the Collection part to is seperate file.

• Identify other potential areas where we could refactor.

• Consider if we should create a seperate contract for the transfer policy roles that the collectible imports

[tomcrown]

Proposal: Refactor collectible.move into Seperate Modules

Here’s my proposed approach:

1. Extract collection.move

• Move all Collection-related structs (Collection, CollectionCap, RenderCap, CollectionTicket) and their events into a new collection.move.
• Relocate functions related to:
  • create_collection, edit_banner, revoke_ownership
  • Attribute schema enforcement (assert_attribute_check)
  • View helpers like get_max_supply
• This keeps collectible.move focused only on collectibles, while collection.move manages lifecycle and metadata of collections.

2. Extract transfer_policy.move

• Move borrow/return helpers for:
  • TransferPolicyCap
  • Display<T> for Collectibles and Attributes
  • Publisher

3. Keep collectible.move Focused

• Collectible<T> struct + functions for:
  • Minting
  • Attribute attach/detach
  • Editing image
  • Burning
• Internal helpers for dynamic fields.

Benefits

• Clear separation of concerns.
• Smaller, more readable modules.
• Easier for new contributors to onboard.

[Reblixt]

Hey @tomcrown Be careful here, Some function argument might need to be modified quite a bit.
But otherwise this is something i was thinking.

If you have any question regarding this please reach out to me! :)

Thanks!