You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
The documentation for cacache.get.info says that the path property in the returned object will contain the filesystem path relative to the cache argument where content is stored. However, this doesn't seem to be the case:
Note that the path property includes the test-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:
It's probably best to update the documentation here to be more clear. This is definitely a wording issue -- changing the path field to be what the docs seem to say would be a pretty impactful breaking change.
Fixeszkat#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 :)
* 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
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: