Skip to content
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

Let test commands be configurable via cargo-process--command-test--additional-args variable #142

Merged
merged 1 commit into from
Oct 12, 2022

Conversation

nfedyashev
Copy link
Contributor

For example, "-- --nocapture" value(instead of default nil) could be used for controlling println! stdout verbosity level of successful tests.

This update is backward compatible for existing users and can only be used for those who really need it.

I thought it is worth updating because, for example, lsp-rust-analyzer-related-tests have this setting enabled by default, along with LSP test runner - ("Run Tests"/"Run test") and for now the only method to achieve it is to patch the plugin.

I wasn't sure whether this variable should contain "-- --nocapture" by default instead, let me know if you want to go this way.

…ditional-args variable

For example, " -- --nocapture" value(instead of default nil) could be used for controlling println! stdout verbosity level of successfull tests
@kwrooijen
Copy link
Owner

Looks good, thanks!

@kwrooijen kwrooijen merged commit e946e36 into kwrooijen:master Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants