about summary refs log tree commit diff
path: root/crates/flycheck
AgeCommit message (Collapse)AuthorLines
2022-07-03Bump cargo_metadataLaurențiu Nicola-1/+1
2022-07-03Bump crossbeam-channelLaurențiu Nicola-1/+1
2022-06-30fix: Fix flycheck sending cancel progress with no running processLukas Wirth-5/+3
2022-06-16Send a DidCancel event when restarting flychecksLukas Wirth-8/+15
2022-06-15PolishLukas Wirth-7/+16
2022-06-13internal: Bring back JodChild into flychecking for cancellationLukas Wirth-24/+53
2022-06-10internal: Bump DependenciesLukas Wirth-3/+3
2022-04-14internal: Show more project building errors to the userLukas Wirth-1/+1
2022-04-05Using `error` instead of `output.stderr` in failure mode.Cadu-2/+2
2022-04-04Made error output the contents of Cargo's stderr as well.Cadu-3/+3
2022-04-04wordsmithing.Cadu-1/+1
2022-04-04Better error message hinting about `cargo clippy`Cadu-1/+1
2022-03-22minor: Bump dependenciesLukas Wirth-6/+6
2021-12-16Bump MSRV (1.57)iDawer-1/+1
2021-11-27Don't discard flycheck error messagesLukas Wirth-1/+1
2021-11-12Allow the check command to terminate without outputWilfred Hughes-2/+2
Cargo will always output something on success: ``` $ cargo check --message-format=json {"reason":"compiler-artifact", ... snipped ... } {"reason":"build-finished","success":true} ``` However, rustc does not output anything on success: ``` $ rustc --error-format=json main.rs $ echo $? 0 ``` Restore the behaviour prior to #10517, where an exit code of 0 is considered good even if nothing is written to stdout. This enables custom overrideCommand values that use rustc rather than cargo.
2021-10-23Set MSRVLaurențiu Nicola-0/+1
2021-10-21Migrate to edition 2021Lukas Wirth-1/+1
2021-10-14a few clippy fixesMilo-1/+1
2021-10-11Remove unnecessary unused attributeLukas Wirth-1/+0
2021-10-11Show cargo check failures to the userLukas Wirth-69/+57
2021-10-03Fix miscellaneous Clippy lintsAramis Razzaghipour-4/+4
2021-10-03Add semicolons for consistencyAramis Razzaghipour-5/+5
`clippy::semicolon_if_nothing_returned`
2021-09-15internal: remove dead codeAleksey Kladov-2/+2
2021-09-03minor: fix some clippy lintsLukas Wirth-6/+1
2021-08-30switch `log` crate to `tracing`Dezhi Wu-4/+4
2021-07-17internal: a bit more of cwd safety for flycheckAleksey Kladov-6/+7
2021-07-09cargo_metadata 0.14kjeremy-1/+1
Removes the following dependent crates: * semver-parser * pest * ucd-trie Removes project_model's dependency on itertools
2021-07-08This patch shortens the spawned threads' names, as threads on LinuxManas-2/+2
have an upper limit of 16 characters for their names.
2021-07-08Explicitly name all spawned threadsManas-2/+8
The thread name is shown in debugger as well as panic messages and this patch makes it easier to follow a thread instead of looking through full backtrace, by naming all spawned threads according to their functioning.
2021-07-05minor: drop dummy authors fieldAleksey Kladov-1/+0
2021-05-12Use package root as `cargo check` working directoryBrendan Cully-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.
2021-04-19Code review feedback.James Leitch-15/+16
2021-04-18Flycheck tries to parse both Cargo and Rustc messages.James Leitch-22/+46
2021-03-02Bump cargo_metadataLaurențiu Nicola-5/+4
2021-01-28Make logger-based debugging more pleasantAleksey Kladov-1/+15
2021-01-11Unfreeze cargo_metadatakjeremy-1/+1
It now pulls in a newer version of semver-parser.
2021-01-08Refactor out JodChildEdwin Cheng-22/+2
2020-11-25Pin cargo_metadatakjeremy-1/+1
2020-10-20Update cratesJeremy Kolb-1/+1
This brings in a number of new dependencies though.
2020-10-13Bump crossbeam-channel in cratesLaurențiu Nicola-1/+1
2020-09-27Spawn a flycheck instance per workspaceJonas Schievink-7/+17
2020-08-24Add description for crates that will be publishedPavan Kumar Sunkara-0/+1
2020-08-24Add version to deps in cargo.tomlPavan Kumar Sunkara-1/+1
2020-08-13Rename ra_ide -> ideAleksey Kladov-3/+4
2020-08-12Rename ra_toolchain -> toolchainAleksey Kladov-2/+2
2020-08-11Log the command flycheck runs to debug misconfigurationsVeetaha-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
2020-07-30flycheck: Added checkOnSave.noDefaultFeaturesClemens Wasser-3/+10
This commit adds the option `rust-analyzer.checkOnSave.noDefaultFeatures` and fixes #5550.
2020-07-29cargo_metadata 0.11.1 and cargo updatekjeremy-1/+1
2020-07-21TypoAleksey Kladov-3/+3
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 20:51:12 +0000