You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my workspace project we use vendored dependencies in the vendor directory, but we do not add the replace-with configuration in the .cargo/config.toml because doing so effectively cuts off all access to crates.io. Instead we use aliases for build and test that set the replacement for those commands e.g.:
I'd like to be able to replicate something like this in rust-analyzer in VS Code for running tests.
What I've tried:
Creating a supplemental config.vendor.toml with the required source settings and setting --config .cargo/config.vendor.toml in rust-analyzer.cargo.extraArgs
Setting the --config source.vendored-sources... etc, in rust-analyzer.cargo.extraArgs
In my workspace project we use vendored dependencies in the
vendor
directory, but we do not add thereplace-with
configuration in the.cargo/config.toml
because doing so effectively cuts off all access to crates.io. Instead we use aliases for build and test that set the replacement for those commands e.g.:I'd like to be able to replicate something like this in rust-analyzer in VS Code for running tests.
What I've tried:
config.vendor.toml
with the required source settings and setting--config .cargo/config.vendor.toml
inrust-analyzer.cargo.extraArgs
--config source.vendored-sources...
etc, inrust-analyzer.cargo.extraArgs
launch.json
and adding either the--config
with a path or with the key/value pairs to the cargo args tables.Is there any way of specifying additional arguments to pass to the invocation of cargo test?
The text was updated successfully, but these errors were encountered: