[Bug] serde_name::trace_name does't work on structs that use #[serde(flatten)]

[tsbernar]

🐛 Bug

Adding #[serde(flatten)] makes trace_name fail to find the name.

To reproduce

Code snippet to reproduce

use serde::{Deserialize, Serialize};

#[derive(Serialize, Deserialize)]
struct MyStruct {
    a: u64,
    b: HashMap<String, serde_json::Value>,
}
#[derive(Serialize, Deserialize)]
struct MyStructFlat {
    a: u64,
    #[serde(flatten)]
    b: HashMap<String, serde_json::Value>,
}

assert_eq!(serde_name::trace_name::<MyStruct>(), Some("MyStruct"));
assert_eq!(serde_name::trace_name::<MyStructFlat>(), None);

Stack trace/error message

n/a

Expected Behavior

Expected behavior is to find the struct name correctly.

System information

Please complete the following information:

Additional context

Add any other context about the problem here.

[banool]

Hey @tsbernar did you manage to fix this somehow?

[tsbernar]

No, I’m still facing this issue

[ma2bd]

serde(flatten) is not supported.

If you work with JSON, maybe this library is closer to what you need? https://graham.cool/schemars/

If you work with both JSON and a binary format tracked by serde-reflection, you can branch the definition of serde::{Serialize,Deserialize} for your struct using is_human_readable, like this: https://github.com/linera-io/linera-protocol/blob/2b46124fff612b25cd8453ec8573ce48e37b214f/linera-version/src/serde_pretty/mod.rs#L20

[ma2bd]

@banool What change in serde 1.0.53 caused the issue?