Commits · 19d8f624ed180e229b57b560764eb3a2875bfaed · dms3 / go-dms3

21 Jan, 2019 1 commit

base32: make GetEncoderFromPath more robust · 19d8f624

Steven Allen authored Jan 21, 2019

Primarily, get rid of extractCidString and cidVer. Neither of these functions
did sane things when a path when a path didn't actually include a CID. For
example, "boo" would yield a base32 encoder.

Also:

* Avoid "optional" errors.
* Make it a pure function of the input path.
* Extract the multibase from *any* type of path of the form
  /namespace/cid-like-thing/... This is a DWIM function.

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>

19d8f624

17 Jan, 2019 2 commits

Don't use ParsePath in extractCidString. · 8209ba61

Kevin Atkinson authored Jan 17, 2019

ParsePath does not preserve the multibase.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>

8209ba61

Add global --cid-base option and enable it for most commands. · b22275fb

Kevin Atkinson authored Nov 22, 2018

This does it on ther server side for most commands.

This also adds a global --output-cidv1 option.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>

b22275fb