-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix offline full path resolution bug
- Loading branch information
1 parent
5853eac
commit 1babd9d
Showing
2 changed files
with
35 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
#!/bin/sh | ||
# | ||
# Copyright (c) 2014 Jeromy Johnson | ||
# MIT Licensed; see the LICENSE file in this repository. | ||
# | ||
|
||
test_description="Test add and cat commands" | ||
|
||
. lib/test-lib.sh | ||
|
||
test_init_ipfs | ||
|
||
test_expect_success "ipfs add file succeeds" ' | ||
echo "some content" > afile && | ||
HASH=$(ipfs add -q afile) | ||
' | ||
|
||
test_expect_success "ipfs cat file suceeds" ' | ||
ipfs cat $HASH > out_1 | ||
' | ||
|
||
test_expect_success "output looks good" ' | ||
test_cmp afile out_1 | ||
' | ||
|
||
test_expect_success "ipfs cat /ipfs/file succeeds" ' | ||
ipfs cat /ipfs/$HASH > out_2 | ||
' | ||
|
||
test_expect_success "output looks good" ' | ||
test_cmp afile out_2 | ||
' | ||
|
||
test_done |
Probably use
"/ipns/"
(with the trailing slash) in the conditional.I'd prefer:
so we can eventually support other protocols besides the current “try all our resolvers” logic we bind to
/ipns/…
. For example, early passes in #1208 had the DNS link stuff under/dns/…
. That was too much to bite off in #1208, but I still think we'll end up with an explicit-protocol system like that eventually, and I want to keep that door easy to re-open when we do decide to move in that direction.Drop
/ipfs/
from this comment to catch up with the condition change. Since this reduces our resolved protocols to just the multi-protocol /ipns/, maybe rephrase the comment to:On the other hand, I really want to roll the pathresolver logic into the recursive namesys helper, since resolving and parsing paths really has very little to do with how your entries are stored. That's a bigger refactoring, so I don't mind tearing up a bit of IPFS special-casing here when I get around to writing it up ;).