- 14 Nov, 2014 14 commits
-
-
Brian Tiger Chow authored
-
Matt Bell authored
-
Brian Tiger Chow authored
@mappum see how the unpacking of arguments happens separately from the resolve loop? It's a bit more verbose, but much clearer. However, doing two different things in one loop is less clear than doing them separately. It also causes problems for further refactoring as it introduces temps that get in the way of further refactorings. Plus, there will be 50+ commands, so it's important that we stay framework agnostic as much as possible. So, this is the style we prefer. It'll keep us nimble in the long run.
-
Matt Bell authored
-
Matt Bell authored
-
Brian Tiger Chow authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Brian Tiger Chow authored
these weren't actually modified when commands2 was introduced. they're exact replicas of the ones that presently exist in core/commands.
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
- 20 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
![](http://m.memegen.com/77n7dk.jpg)
-
- 09 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
- cleaned up cmd help - ipfs name publish [<name>] <ref> - ipfs name resolve [<name>] - publish validates <ref> - both validate n args
-
- 08 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
type NameSystem interface { Resolver Publisher } should say it all. cc @whyrusleeping
-
- 06 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 01 Oct, 2014 5 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Jeromy authored
-
Jeromy authored
-