- OS: Windows
- Version of IPFS Desktop: 0.20.5
Describe the bug
Not all codecs supported by the IPFS command-line are supported by IPFS desktop. See screenshot. It only shows dag-json but also json and some other codecs show the same error.
When making a CID using ipfs dag put someData.json --store-codec=dag-json, I get a CIDv1. Strange enough, dag-json is not in the list of ipfs cid codecs, but supported by ipfs dag put. When copying the received CID to IPFS Desktop, I get error from the screenshot that there is no resolver found for the codec.
To Reproduce
Steps to reproduce the behavior:
ipfs cid codecs
notepad someData.json and add some JSON data
ipfs dag put someData.json --store-codec=dag-json
- Copy the received CID to IPFS Desktop and inspect it.
- See error
Expected behavior
IPFS Desktop recognises that the CID is dag-json, so it should also view information about the content.
Screenshots

Additional context
None.
Describe the bug
Not all codecs supported by the IPFS command-line are supported by IPFS desktop. See screenshot. It only shows
dag-jsonbut alsojsonand some other codecs show the same error.When making a CID using
ipfs dag put someData.json --store-codec=dag-json, I get a CIDv1. Strange enough,dag-jsonis not in the list ofipfs cid codecs, but supported byipfs dag put. When copying the received CID to IPFS Desktop, I get error from the screenshot that there is no resolver found for the codec.To Reproduce
Steps to reproduce the behavior:
ipfs cid codecsnotepad someData.jsonand add some JSON dataipfs dag put someData.json --store-codec=dag-jsonExpected behavior
IPFS Desktop recognises that the CID is
dag-json, so it should also view information about the content.Screenshots

Additional context
None.