1. 23 3月, 2017 2 次提交
  2. 22 3月, 2017 13 次提交
  3. 21 3月, 2017 4 次提交
  4. 20 3月, 2017 1 次提交
  5. 19 3月, 2017 1 次提交
  6. 18 3月, 2017 3 次提交
  7. 17 3月, 2017 2 次提交
    • coreapi: make the interfaces path centric · ee45b8d3
      The new coreiface.Path maps a path to the cid.Cid
      resulting from a full path resolution.
      
      The path is internally represented as a go-ipfs/path.Path,
      but that doesn't matter to the outside.
      
      Apart from the path-to-CID mapping, it also aims to hold all
      resolved segment CIDs of the path. Right now it only exposes
      Root(), and only for flat paths a la /ipfs/Qmfoo. In other cases,
      the root is nil.
      
      In the future, resolution will internally use
      go-ipfs/path.Resolver.ResolvePathComponents and thus always return
      the proper resolved segments, via Root(), or a future Segments() func.
      
      - Add coreiface.Path with Cid() and Root().
      - Add CoreAPI.ResolvePath() for getting a coreiface.Path.
      - All functions now expect and return coreiface.Path.
      - Add ParsePath() and ParseCid() for constructing a coreiface.Path.
      - Add coreiface.Node and Link which are simply go-ipld-node.Node and Link.
      - Add CoreAPI.ResolveNode() for getting a Node from a Path.
      
      License: MIT
      Signed-off-by: 's avatarLars Gierth <larsg@systemli.org>
      Lars Gierth 提交于
    • coreapi: smarter way of dealing with the different APIs · e260d2fd
      License: MIT
      Signed-off-by: 's avatarLars Gierth <larsg@systemli.org>
      Lars Gierth 提交于
  8. 16 3月, 2017 4 次提交
  9. 15 3月, 2017 1 次提交
  10. 13 3月, 2017 1 次提交
  11. 11 3月, 2017 4 次提交
  12. 10 3月, 2017 4 次提交