diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-10-02 10:42:03 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-10-02 10:42:03 +0100 |
| commit | d8e5265309cf92857c996d4f55372e3b431468bf (patch) | |
| tree | 101f5f55c324d7cb7bf3c7ae22a553ca4f7bf66c /crates/flycheck | |
| parent | 40a028c9a837f4f189b7db82cd4034536af87322 (diff) | |
| parent | 4ebacf9024d82349c4b95826a4a791bdf384d0df (diff) | |
Merge #5954
5954: Add flexible configuration for runnables r=popzxc a=popzxc
This PR introduces two new configuration options for runnables: `overrideCargo` and `cargoExtraArgs`.
These options are applied to all the "run" tasks of rust analyzer, such as binaries and tests.
Overall motivation is that rust-analyzer provides similar options, for example, for `rustfmt`, but not for runnables.
## `overrideCargo`
This option allows user to replace `cargo` command with something else (well, something that is compatible with the cargo arguments).
Motivation is that some projects may have wrappers around cargo (or even whole alternatives to cargo), which do something related to the project, and only then run `cargo`. With this feature, such users will be able to use lens and run tests directly from the IDE rather than from terminal.
## `cargoExtraArgs`
This option allows user to add any additional arguments for `cargo`, such as `--release`.
It may be useful, for example, if project has big integration tests which take too long in debug mode, or if any other `cargo` flag has to be passed.
Co-authored-by: Igor Aleksanov <[email protected]>
Diffstat (limited to 'crates/flycheck')
0 files changed, 0 insertions, 0 deletions