extension: New ft metadata api types broken

After merging: https://github.com/hirosystems/wallet/pull/3439 we need to make sure types are coordinated with the change bc some props appear to come in undefined.

cc @rafaelcr is this expected?

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (12 by maintainers)

Most upvoted comments

ah, sorry about that… could you open an issue in the Metadata API repo? we can continue there (while I fix this) @fbwoolf

@fbwoolf there’s an issue with that specific contract which I’m currently fixing… see: https://api.hiro.so/metadata/v1/nft/SP3D6PV2ACBPEKYJTCMH7HEN02KP87QSP8KTEH335.megapont-robot-component-nft/48346

Sorry about that @fbwoolf I just noticed the package I published did not include several files… could you try again with version 1.0.2?

Yep, that worked, thanks!

Sorry about that @fbwoolf I just noticed the package I published did not include several files… could you try again with version 1.0.2?

Some tokens might have failed during metadata fetch. In that case, you’ll get a 422 response with that error message

Thanks for feedback, I’ll put up a patch to fix it until you have types ready. 👍

Oh ok yeah I still need to generate types for this API, opened https://github.com/hirosystems/token-metadata-api/issues/132

I see what is happening I think, token metadata is coming in as not found…

Some tokens might have failed during metadata fetch. In that case, you’ll get a 422 response with that error message