-
Notifications
You must be signed in to change notification settings - Fork 15
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
empty resources
on this nft
#265
Comments
Hello, can you please rephrase your question? Or provide more context? |
hi @vikiival, how to get the image for this item https://canary.kodadot.xyz/ksm/gallery/15635794-54bbd380dc3baaa27b-EVRLOOT-ADVANCED_FISHINGROD-2 return |
Another item in the same collection we can get the |
{
"data": {
"token": {
"id": "15635794-54bbd380dc3baaa27b-EVRLOOT-ADVANCED_FISHINGROD-2",
"metadata_name": "Reinforced Palm Rod",
"rootowner": "EVRLT14nteG7mp31N4cmTTpYdDnjxEr25zQwXKC3Suph6L2",
"resources": [],
"equipped": null
}
}
} Hello, this is not an issue of our indexer, I checked against RMRK Prod API and NFT does not contain any resources |
I see, so it was expected then do we need to adjust our UI? maybe tell the user "Media not found for this item" |
anyway, when I search "Reinforced Palm Rod" on singular they show only "439 results" on our UI, shows "444 items" https://canary.kodadot.xyz/ksm/collection/54bbd380dc3baaa27b-EVRLOOT?search=Reinforced%20Palm%20Rod |
how to hide it in our query? currently this is our query without query, the total items in that collection: |
as the smart man (@preschian) said:
{
"data": {
"nftEntityById": {
"meta": {
"name": "Reinforced Palm Rod",
"image": null,
"animationUrl": null
}
}
}
} So dumb approach is to hide it on frontend, |
ok, I think it's better to wait TokenEntity implemented then |
I can only fix the "More from this collection" section
for this specific nft seems like from the indexer side. on rmrk2 at least need some
resources
. this nftmeta.image
andresources
was emptyOriginally posted by @preschian in kodadot/nft-gallery#6599 (comment)
The text was updated successfully, but these errors were encountered: