fix(NFT Images): Support array image types for CIP-68 #922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the recommendation of the pool.pm team and in compliance with metadata standards, we sometimes see NFT IPFS links represented as arrays of strings. These arrays are meant to be concatenated directly to produce the IPFS link (or data scheme, etc.).
Because the image is retrieved in the send assets page, without this change users are UNABLE to send assets in CIP-68 format (since the decimals do not get properly set in
nami/src/api/extension/index.js#1762
).[ Testing: npm test, manually built and submitted tx from Nami ]
[ Test Artifacts: txn 5e342b856efa596da433e3eec4256809cfe9bd9c4c9c39eb316328080ced13f1 ]