-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
Tests: use minimal configuration by default #459
Conversation
I kept |
yeah i kinda wanna keep backwards compatibility. No real need to a breaking change here. thanks for the PR :) can you fix the stylua ci? thanks |
I fixed it by the way. I also tested the PR against |
thanks :) |
…plugin otherwise its a breaking change, see nvim-treesitter/nvim-treesitter#4856
using |
…plugin otherwise its a breaking change, see nvim-treesitter/nvim-treesitter#4856
…plugin otherwise its a breaking change, see nvim-treesitter/nvim-treesitter#4856
…plugin (#497) otherwise its a breaking change, see nvim-treesitter/nvim-treesitter#4856
This was reverted in #497. So for now, as per #497 we will use user's Can we have this back again? |
Previously, when running
PlenaryBusted
commands, all plugins were being loaded.{ minimal = true }
wouldn't work either because plenary must be loaded,--noplugin
would prevent that.{ minimal_init = path }
had the same problem.Solution:
minimal
andminimal_init
are still recognized and will have the effect of adding the--clean
argument, but most of the times they can be omittedminimal_init
will still be sourcedminimal
is the same as no options, so it can be omitted--clean
I couldn't make it work in Windows though (neither before).