-
Notifications
You must be signed in to change notification settings - Fork 290
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
aliases for tool backend #2885
Comments
I have what I think is a practical example of the usefulness of this. I was trying to use the Something like perhaps: [registry]
sarif-fmt = "ubi:psastras/sarif-rs"
shellcheck-sarif = "ubi:psastras/sarif-rs"
[tool]
sarif-fmt = "sarif-fmt-v0.6.6"
shellcheck-sarif = "shellcheck-sarif-v0.6.6" That said my issue might be hinting more at a way to have multiple versions of the same tool (with an alias for the command) active at the same time. |
thinking about this more I'm starting to prefer this as the config: [alias] # shorthand for `alias.docuum.full = "cargo:docuum"`
docuum = "cargo:docuum"
[alias.docuum] # long version
full = "cargo:docuum"
versions = {lts = "20"} # in case you want to alias the name and the versions Of course this would still do the same thing as today for backwards-compatibility, but I probably would remove it from the docs: [alias.node]
lts = "20" |
I'm trying to test this but it doesn't seem to work… am I using it right?
And then with
I get
|
it won't do anything if the plugin is already installed with that name |
right now the
[aliases]
portion ofmise.toml
is designed for tool versions:however, what we don't have is a way for us to do this with the tool backend:
I'm not sure how we might want to present this. The above is my first thought, but it wouldn't allow having both aliased versions and aliased backend, so that would need to be figured out. A couple of alternatives:
"registry" might be ideal here since it maps reasonably well to the codebase, and maybe it could allow for alternate registries like we have for the old asdf-specific shortname stuff
The text was updated successfully, but these errors were encountered: