This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 29
cacache.get.info returning path including cache dir, not relative path #165
Comments
It's probably best to update the documentation here to be more clear. This is definitely a wording issue -- changing the Would you be up to filing a PR to fix the docs? |
Yep, can do! |
hdgarrood
added a commit
to hdgarrood/cacache
that referenced
this issue
Jun 16, 2019
Fixes zkat#165. I don't speak Spanish but I made an attempt at updating README.es.md too, based on the "joined with `cachePath`" comments I saw in the `ls` docs; hopefully what I've got here makes sense :)
zkat
pushed a commit
that referenced
this issue
Jun 16, 2019
* Fix docs for `path` property in get.info Fixes #165. I don't speak Spanish but I made an attempt at updating README.es.md too, based on the "joined with `cachePath`" comments I saw in the `ls` docs; hopefully what I've got here makes sense :) * Update README.es.md
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The documentation for
cacache.get.info
says that thepath
property in the returned object will contain the filesystem path relative to thecache
argument where content is stored. However, this doesn't seem to be the case:Note that the
path
property includes thetest-cache/
prefix, whereas based on the docs I would have expected it to not include that prefix. I opened an issue because I'm not sure if this is a bug or a documentation error (or if I'm just misinterpreting).The text was updated successfully, but these errors were encountered: