Replies: 1 comment 1 reply
-
Plugins definitely aren't going away. You can have plugins that only modify env vars and don't provide tools. In asdf, the concept of tools and plugins were one in the same. mise started with that but now that we have backends the concepts need to be separated. I actually don't think this is going to be that confusing, except for some places in the docs/code where "plugins" is still conflated to mean "tool". I've been able to move a lot of the tools over to aqua, especially more popular ones. The exposure to asdf plugins should diminish over time as we can leverage aqua/ubi more. "Plugins" is going to be a term specific to extending functionality in mise, whether that's adding a tool or doing something else. I think this is more typical of the term generally anyhow. |
Beta Was this translation helpful? Give feedback.
-
Original title: Deprecate and remove "plugins" concept and fully move to aliases
It seem that mise is leaning more heavily on the concepts of "tools, aliases, and backends" vs "traditional asdf & vfox plugins", and I was wondering if you want to go all in to make mise simpler to understand and work with, or continue support the concept of plugins.
This includes:
Problems of having plugins concept in mise today:
mise plugin add x y
creates something like an alias but not quite.Challenges of removing the plugins concept:
Beta Was this translation helpful? Give feedback.
All reactions