-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Argument to version command - path or dependency name? #226
Comments
Hello @straight-shoota, the reasoning for the second argument is explained in the pull request, which is a response to the RFC #147. See #147 (comment) for the specific use case. |
Ah, somehow I missed that. Thanks for pointing it out. The example in the linked comment should also work with |
I suppose we could have |
For backwards compatibility, it could even treat |
Since there has been no PR for this issue so far, I will remove it from the milestone v0.10.0 |
I would suggest to close this issue in favour of a more general approach to querying information (including the version) of installed shards (see #86 (comment)). |
#148 introduced
shards version
command which prints the version specified inshard.yml
. The command accepts an optional parameterpath
which can be used to specifiy to look forshard.yml
in a different path.@luislavena Was there a specific reason for this feature?
To me, it feels a little bit strange. I mean, it being able to specify a different directory is nice, but wouldn't that make sense for all commands? Similar to
make -C path
. I think it is better to use a named option. It is not intuitive that the first argument toversion
is interpreted as a path to look for ashard.yml
.I'd rather suggest
shards version
to have an argument to specify a dependency name and it would print the installed version of that dependency.For example, inside
shards
directory,shards version minitest
would print0.3.5
.The text was updated successfully, but these errors were encountered: