Steven Allen 09a4311db7 test: fix put with hash test ... We just changed ID/"id" to IDENTITY/"identity" to match the multicodec table and avoid confusion with peer IDs, CIDs, etc. Unfortunately, this breaks the `--hash=id` flag. Luckily, I'm pretty sure nobody's actually using this. As putting a block with an identity hash is useless. If they are users, we can go about adding in backwards compatibility hacks later. This commit was moved from ipfs/interface-go-ipfs-core@6ebdbe7ef3 This commit was moved from ipfs/boxo@3b9a723861		2019-08-23 16:22:22 -07:00
..
options	Update Pin.RmRecursive docs to clarify shared indirect pins are not removed	2019-03-29 16:16:16 -07:00
path	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
tests	test: fix put with hash test	2019-08-23 16:22:22 -07:00
block.go	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
coreapi.go	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
dag.go	gx-go uw	2019-02-09 01:23:13 +01:00
dht.go	migrate to go-libp2p-core.	2019-05-28 17:09:34 +01:00
errors.go	errors: introduce a 'not supported' error	2019-02-19 02:44:36 -08:00
key.go	migrate to go-libp2p-core.	2019-05-28 17:09:34 +01:00
name.go	path: WIP	2019-04-04 09:00:23 +02:00
object.go	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
pin.go	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
pubsub.go	migrate to go-libp2p-core.	2019-05-28 17:09:34 +01:00
swarm.go	migrate to go-libp2p-core.	2019-05-28 17:09:34 +01:00
unixfs.go	path: rename ParsePath and ResolvedPath	2019-04-04 09:00:23 +02:00
util.go	Cleanup instances of manual resolver construction	2018-10-02 18:35:14 +02:00