You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The getDetails methods for ERC721Standard and ERC1155Standard currently fetch and return a tokenURI. Ideally they would fetch the tokenURI and then use it to fetch other more useful details like imagename and description (possibly more) as we do in the getCollectibleInformationFromTokenURI method of the CollectiblesController.
The text was updated successfully, but these errors were encountered:
sounds right, getTokenURI should return the UR and getDetails should resolve it.
I'm thinking about the case the tokenURI is a data URI, or a decentralized fs protocol like IPFS, for now we'll support https protocol only, right?
And We currently support fetching data from IPFS in getCollectibleInformationFromTokenURI. I don't see why we shouldn't in this case as well? cc @wachunei
The
getDetails
methods forERC721Standard
andERC1155Standard
currently fetch and return a tokenURI. Ideally they would fetch the tokenURI and then use it to fetch other more useful details likeimage
name
anddescription
(possibly more) as we do in thegetCollectibleInformationFromTokenURI
method of theCollectiblesController
.The text was updated successfully, but these errors were encountered: