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
Provide a flag or configuration option to allow asdf install
to continue when missing plugins are found in .tool-versions
#1123
Comments
There are a couple different ways we could solve this:
To me, options 2 and 3 seem like the best. Thoughts? |
I am ok with both approaches. To be honest, it is a matter of deciding which one is the most common case (2 or 3) and make that one the default. Other option could be to make the default depend on the |
This is one of the reasons I dislike the Thinking out loud. As I understand, it was introduced so people could easily setup a project on their system with little effort. The notion of blocking on a plugin not existing is because you want to ensure you have all the tools for the project you're currently working on. Global management of tools perhaps fits outside the initial I feel that the per-project usability of Perhaps, we treat the "global" ( Perhaps |
Being honest, I dislike the idea of having different behaviours depending on the directory. That is inconsistent and hard to explain for newcomers. If someone decides to locate a project in the home directory (odd decision, but still a decision), that person would be wondering why it didn't work as expected. I would rather go for a solution where things behave consistently, but the behaviour can be changed. |
This change breaks my workflow as I intentionally do not install all plugins on all my machines (depending on which I need). Is there any way to disable this feature (looking at the code I guess no) or make it so it can be disabled?
Originally posted by @cmur2 in #1033 (comment)
The text was updated successfully, but these errors were encountered: