Closed LeonardoMor closed 3 months ago
Do you think some kind of ignore list would be enough?
I personally have my mason install path added to my system path. This way I just let mason handle all my tools that nvim uses, and I get the benefit of having all my tool versions under version control with https://github.com/zapling/mason-lock.nvim.
It didn't occur to me, but an ignore list is probably the most satisfying solution and the easiest to implement :)
@LeonardoMor this should now be resovled with the latest commit on main :) https://github.com/zapling/mason-conform.nvim/commit/882a4449e5a2e81f5441d837d74d356e03617660
You can now pass in an optional { ignore_install = {'prettier'} }
when calling the setup
function.
Some tools will be present on the conform config but do not need to be installed by Mason. For example, I might have
prettier
installed system-wide. Orjq
orxmllint
.It will be beneficial to try to detect, any given tool, whether it is already installed or not. This will avoid duplicates and desired behavior.