-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add metadata views doc #448
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
# About NFT MetadataViews on Flow | ||
|
||
`MetadataViews` on Flow offers a standardized way to represent metadata across different NFTs. With its integration, developers can ensure that different platforms and marketplaces can interpret the NFT metadata in a unified manner. This means that when you go to a marketplace, it looks and reads the same on this marketplace as it does on another, providing a consistent user experience across different platforms. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to represent metadata like...across different NFTs
Would add a couple examples here
return MetadataViews.NFTCollectionData( | ||
storagePath: ExampleNFT.CollectionStoragePath, | ||
publicPath: ExampleNFT.CollectionPublicPath, | ||
providerPath: /private/exampleNFTCollection, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be a string, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no it is a path, put private paths are going away so should we create a new Collection view?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean we do not need type anymore after stable cadence, atleast not more then 1 type.
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
…ow/docs into chasefleming/metadata-views
I'm gonna pull this branch down and make a PR to it to add my edits, so don't merge it yet |
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
Co-authored-by: Greg Santos <[email protected]>
No description provided.