Bug Description
When creating a de-facto keyed collection of inputs on the command-line paths that start with ~ do not work. It does not find the artifact then errors out on the key as if it were a bad cache. We need to expand the ~ to be the home directory if it is at the head of the path. Click does this on its own if it just receives a path like ~/foo, but if it gets a key:path like bar:~/foo it obviously doesn't understand that it needs to expand that ~.
Steps to reproduce the behavior
Pick an action that takes a Collection of inputs
Give the collection a keyed member with a path starting with ~
See it get confused
Expected behavior
It should actually find the artifact.
Screenshots
You can see that it found the foo keyed artifact, so the artifact does exist, but for the bar keyed one the path starting with ~ confused it into not finding the artifact.
Bug Description When creating a de-facto keyed collection of inputs on the command-line paths that start with
~do not work. It does not find the artifact then errors out on the key as if it were a bad cache. We need to expand the~to be the home directory if it is at the head of the path. Click does this on its own if it just receives a path like~/foo, but if it gets a key:path likebar:~/fooit obviously doesn't understand that it needs to expand that~.Steps to reproduce the behavior
~Expected behavior It should actually find the artifact.
Screenshots You can see that it found the
fookeyed artifact, so the artifact does exist, but for thebarkeyed one the path starting with~confused it into not finding the artifact.Computation Environment