Add a get IRC27NFT Metadata guide

[Ginowine]

Description of change

This PR creates a new page titled "Get NFT Metadata". The page explains how to utilize the getIRC27NFTData function within a smart contract to fetch information about a specific IRC27 NFT on the IOTA Network

Links to any relevant issues

fixes #1571

Type of change

• Documentation Enhancement

Change checklist

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own changes
• I have made sure that added/changed links still work
• I have commented my code, particularly in hard-to-understand areas

[lucas-tortora]

Very nice article :) just some suggestions regarding structure

[Ginowine]

I have addressed all the review suggestions. Please take a look and let me know if there are any further changes needed.

[Ginowine]

I noticed this URL (../../../reference/magic-contract/ISCSandbox/#getirc27nftdata) on the page is causing the test/build to fail. Trying to get the right URL. Will send a new PR after fixing it

[Dr-Electron]

Really great article ❤️
I would like to change it a little bit tho.

Let me first try to explain the "issue".
When you send an NFT on L1 to the L1 account of the chain, it gets automatically registered as ERC721 token in our EVM. But as your IRC27 token is not fully compatible with the tokenUri of ERC721 which returns a json, our EVM creates that json out of the uri, the description and the name of the IRC27 NFT on L1.

So normally people would never use the getIRC27NFTData function. The would just call the standard tokenUri of ERC721.

So with that in mind, I think the first thing we should do, is is adding an admonition that tells people to use tokenUri if possible. Only if the need some of the unique metadata of IRC27 they should use this (or technically if they develop something themselves to transfer this NFTs or whatever).

This also means we are more interested in decoding the metadata.uri.

Btw you can see how this function is used to get the tokenUri here

So TL:DR;

• Add admonition pointing people to https://wiki.iota.org/isc/how-tos/core-contracts/nft/use-as-erc721/ and telling them about the tokenUri
• Rewrite encoding to actually decode the JSON from metadata.uri.

[Dr-Electron]

As discussed on slack I think we can get rid of the encoding stuff. Sorry for realising that soo late.

Also you need to change version 1.3. In 1.1 some of this things are not available yet.

So I would move it to version 1.3 and we can think if it makes sense to add a stripped down version to 1.1, but I think just adding it to 1.3 should be fine.

[Ginowine]

Ok, thanks for the suggestions. I'll implement them and send a new push request.

[Ginowine]

@Dr-Electron, I have updated the doc to follow your suggestions. Please take a look and let me know. Thanks.

[lucas-tortora]

@Dr-Electron, I have updated the doc to follow your suggestions. Please take a look and let me know. Thanks.

@Ginowine, could you fix the broken links in the test workflow?

[Ginowine]

@lucas-tortora, I fixed the link pointing to the mint-nft.md file. For the other link errors below, Kevin said the preview doesn’t work because my fork doesn’t know iota-wiki deployment secrets and that we can ignore it as long as the build workflow succeeds.

../../../reference/magic-contract/ERC721NFTs.md/#tokenuri (resolved as: /isc/v1.3-alpha/how-tos/reference/magic-contract/ERC721NFTs.md/)

The below link was provided by Kevin.

../../../reference/magic-contract/ERC721NFTs.md#tokenuri

It would be great if I could get the correct link to use.

[lucas-tortora]

this should fix the build :)

[Ginowine]

Thank you so much, @lucas-tortora, for the suggestions on how to fix the build. Noted.

[Dr-Electron]

LGTM, just pushed a formatting fix and added the page to the sidebar in version 1.3.

Once we move this example into the wasp repo I would prefer using the using for pattern to import the asNFTID() library function to be able to use it on variables directly. I prefer that syntax. It is way clearer imo