aboutsummaryrefslogtreecommitdiff
path: root/crates/flycheck
Commit message (Collapse)AuthorAgeFilesLines
* Use package root as `cargo check` working directoryBrendan Cully2021-05-131-0/+1
| | | | | | | | | | | | | | | 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.
* Code review feedback.James Leitch2021-04-191-15/+16
|
* Flycheck tries to parse both Cargo and Rustc messages.James Leitch2021-04-192-22/+46
|
* Bump cargo_metadataLaurențiu Nicola2021-03-022-5/+4
|
* Make logger-based debugging more pleasantAleksey Kladov2021-01-281-1/+15
|
* Unfreeze cargo_metadatakjeremy2021-01-111-1/+1
| | | | It now pulls in a newer version of semver-parser.
* Refactor out JodChildEdwin Cheng2021-01-072-22/+2
|
* Pin cargo_metadatakjeremy2020-11-251-1/+1
|
* Update cratesJeremy Kolb2020-10-201-1/+1
| | | | This brings in a number of new dependencies though.
* Bump crossbeam-channel in cratesLaurențiu Nicola2020-10-131-1/+1
|
* Spawn a flycheck instance per workspaceJonas Schievink2020-09-271-7/+17
|
* Add description for crates that will be publishedPavan Kumar Sunkara2020-08-241-0/+1
|
* Add version to deps in cargo.tomlPavan Kumar Sunkara2020-08-241-1/+1
|
* Rename ra_ide -> ideAleksey Kladov2020-08-131-3/+4
|
* Rename ra_toolchain -> toolchainAleksey Kladov2020-08-122-2/+2
|
* Log the command flycheck runs to debug misconfigurationsVeetaha2020-08-111-2/+8
| | | | | | | | | | | | Without this users have no clue why flycheck fails to run. This is what is printed to the output channel: ``` [ERROR rust_analyzer::main_loop] cargo check failed: Cargo watcher failed,the command produced no valid metadata (exit code: ExitStatus(ExitStatus(25856))) ``` I stumbled with this figuring out that rust-analyzer adds `--all-features` which is not intended for some crates in the workspace (e.g. they have mutually-exclusive features. Having the command rust-analyzer ran should help a lot
* flycheck: Added checkOnSave.noDefaultFeaturesClemens Wasser2020-07-301-3/+10
| | | | | | This commit adds the option `rust-analyzer.checkOnSave.noDefaultFeatures` and fixes #5550.
* cargo_metadata 0.11.1 and cargo updatekjeremy2020-07-291-1/+1
|
* TypoAleksey Kladov2020-07-211-3/+3
|
* Propagate cargo.target to checkOnSaveAleksey Kladov2020-07-211-0/+6
|
* Add a license field to all the cratesYuki Okushi2020-07-141-0/+1
|
* Cleanup diagnostic conversion codeAleksey Kladov2020-07-091-1/+2
|
* Log flycheck commandAleksey Kladov2020-07-011-0/+1
|
* Cleanup cargo process handling in flycheckAleksey Kladov2020-06-281-60/+61
|
* More standard pattern for CargoAleksey Kladov2020-06-281-76/+83
|
* NamingAleksey Kladov2020-06-281-8/+7
|
* RenameAleksey Kladov2020-06-281-3/+3
|
* Make sure to join the childAleksey Kladov2020-06-281-2/+25
|
* Be more precise about flycheck statusAleksey Kladov2020-06-261-62/+30
|
* Refactor main_loopAleksey Kladov2020-06-251-10/+7
|
* Canonicalize actor APIAleksey Kladov2020-06-251-69/+55
|
* SimplifyAleksey Kladov2020-06-251-15/+6
|
* Minor renameAleksey Kladov2020-06-251-28/+29
|
* Rename ra_flycheck -> flycheckAleksey Kladov2020-06-252-0/+358