# Use rust-analyzer's flycheck as source of cargo diagnostics \(\#29779\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/ba59305510d14d8a02cdcd7835793eadaaa818d3)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: ba59305510d14d8a02cdcd7835793eadaaa818d3

Requested commit: ba59305510d14d8a02cdcd7835793eadaaa818d3

Commit: ba59305510d14d8a02cdcd7835793eadaaa818d3

Tree: 1ef975357abe01405869ed8668abd7139c65ea07

Author: Kirill Bulatov

Committer: GitHub

## Message

```
Use rust-analyzer's flycheck as source of cargo diagnostics (#29779)

Follow-up of https://github.com/zed-industries/zed/pull/29706

Instead of doing `cargo check` manually, use rust-analyzer's flycheck:
at the cost of more sophisticated check command configuration, we keep
much less code in Zed, and get a proper progress report.

User-facing UI does not change except `diagnostics_fetch_command` and
`env` settings removed from the diagnostics settings.

Release Notes:

- N/A
```

## Parents

- [672a1dd5537dda4114a0814dd361b9bc0ce1778d](https://git.cafe/gitcafe/zed/commit/672a1dd5537dda4114a0814dd361b9bc0ce1778d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/ba59305510d14d8a02cdcd7835793eadaaa818d3?format=markdown)