Use serde 1.0.221 instead of serde_derive hackery (#38137)

serde 1.0.221 introduced serde_core into the build graph, which should
render explicitly depending on serde_derive for faster build times an
obsolote method.

Besides, I'm not even sure if that worked for us. My hunch is that at
least one of our deps would have `serde` with derive feature enabled..
and then, most of the crates using `serde_derive` explicitly were also
depending on gpui, which depended on `serde`.. thus, we wouldn't have
gained anything from explicit dep on `serde_derive`

Release Notes:

- N/A
This commit is contained in:
Piotr Osiewicz
2025-09-14 14:01:04 +02:00
committed by GitHub
parent 2b1f7d5763
commit 37239fd66b
40 changed files with 144 additions and 53 deletions
+1 -1
View File
@@ -3,7 +3,7 @@ use gpui::{Action, Context, Window, actions};
use language::Point;
use schemars::JsonSchema;
use search::{BufferSearchBar, SearchOptions, buffer_search};
use serde_derive::Deserialize;
use serde::Deserialize;
use settings::Settings;
use std::{iter::Peekable, str::Chars};
use util::serde::default_true;