# Fix some warnings/issues uncovered by the new cfg checking \(\#12310\) · gitcafe/zed

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

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

Visibility: public

Requested revision: a1e5b122e7d816934727e48f66a8b505f2dcbd71

Requested commit: a1e5b122e7d816934727e48f66a8b505f2dcbd71

Commit: a1e5b122e7d816934727e48f66a8b505f2dcbd71

Tree: bd4249f06066d180c8fdb552e439b16b8145f480

Author: Jakob Hellermann

Committer: GitHub

## Message

```
Fix some warnings/issues uncovered by the new cfg checking (#12310)

Rust recently got the ability to check for typos or errors in `cfg`
attributes: https://blog.rust-lang.org/2024/05/06/check-cfg.html
This PR fixes the new warnings.

- gpui can be run with `RUSTFLAGS="--cfg gles"`, make this explicit in
`[workspace.lints.rust]`
- `cfg!(any(test, sqlite))` was just a bug, it should be
`feature(sqlite)`
- the `languages` crate had a `#[cfg(any(test, feature =
"test-support"))]` function without ever declaring the `test-support`
feature
- the `MarkdownTag` enum had a `cfg_attr` for serde without actually
having serde support


Now the only warnings when building are unused fields
`InlayHover.excerpt`, `SavedConversationMetadata.path` ,
`UserTestPlan.allow_client_reconnection` and `SyntaxMapCapture.depth`.

Release Notes:

- N/A
```

## Parents

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

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