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
{{ message }}
This repository has been archived by the owner on Sep 3, 2021. It is now read-only.
We should emit a warning first time .codec property is accessed, that provides link to the instructions for migration from .codec to .code. Current plan is to have it indefinitely, that is until we ipfs ecosystem migrates to js-multiformats.
The reason we want warnings is because users usually get CID e.g. by calling const { cid } = await ipfs.add(...), so this could provide room for migration instead of clean break.
The text was updated successfully, but these errors were encountered:
@mikeal do you mind creating a markdown file in the repo that warning could point at. I think you have much clear understanding of this than anyone else.
We should emit a warning first time
.codec
property is accessed, that provides link to the instructions for migration from.codec
to.code
. Current plan is to have it indefinitely, that is until we ipfs ecosystem migrates tojs-multiformats
.The reason we want warnings is because users usually get
CID
e.g. by callingconst { cid } = await ipfs.add(...)
, so this could provide room for migration instead of clean break.The text was updated successfully, but these errors were encountered: