diff options
author | Brendan Cully <[email protected]> | 2021-05-13 03:50:52 +0100 |
---|---|---|
committer | Brendan Cully <[email protected]> | 2021-05-13 03:50:52 +0100 |
commit | c4664609ed0f8b430285de99b4f7a8cc0ae655f5 (patch) | |
tree | f582688a7fd396b5f18cd215d08af12b1e9d4b51 /crates/syntax/test_data/parser/err/0043_weird_blocks.rs | |
parent | 312f1fe20a6a0a8e69834c66f51b9abc9db5e0ce (diff) |
Use package root as `cargo check` working directory
Cargo commands are affected by the `.cargo/config` files above
their working directory. If cargo is invoked from above the directory
holding `Cargo.toml`, it may not pick up important settings like
registry replacements, causing it to behave differently or even fail.
Most cargo invocations are currently setting their working directories
to the directory containing `Cargo.toml`, but a couple of paths remain
in which cargo is invoked from the default workspace root instead.
This change fixes that, resolving some cargo check failures that I
experienced in a multi-root workspace in which packages used different
registries.
Diffstat (limited to 'crates/syntax/test_data/parser/err/0043_weird_blocks.rs')
0 files changed, 0 insertions, 0 deletions