Add Option<ObjectId> serialize_object_id_as_hex_string support about bson-rust HOT 3 CLOSED

Hey @Chu-4hun, thanks for filing this issue! Unfortunately the serde helpers we provide are fairly brittle when it comes to working with optional/nested types. I discussed this issue with the team and we'd prefer not to add duplicates of the helpers for these types; however, we did discuss converting the helpers to serde_with::(De)SerializeAs implementations to allow for more flexibility in use cases like yours. We don't have the bandwidth for this work right now (and it would be a breaking change), but I filed RUST-1748 for consideration in the next major version.

In the meantime, I'd recommend using your own custom serialization method. The following should do the trick:

fn serialize_object_id_option_as_hex_string<S: Serializer>(
    val: &Option<ObjectId>,
    serializer: S
) -> Result<S::Ok, S::Error> {
    match val {
        Some(oid) => oid.to_hex().serialize(serializer),
        None => serializer.serialize_none(),
    }
}

from bson-rust.

I'm trying to rewrite a backend in rust and this is one of the first thing I stumbled across.

We have a MongoDB collection where some documents have optional references to other documents.

These references can be null, so like the example above I'm using Option<ObjectId> to store the value.

isabelatkinson's workaround does the job, but shouldn't this be included by default? Feels awkward to keep a helper snippet of code around for a basic task like this.

Please reconsider to support this somehow. Or make it at least clearer in the documentation and provide some guidance for people who just stumbled across this.

I mean, the main idea is to have a simple hex representation of an ObjectID (in my case, for a REST API). I imagine a lot of other developers are facing the same issue. If so, are there better workarounds for this?

Anyway, I'd like to +1 this.

from bson-rust.

Thanks for the reply. Glad I could help

from bson-rust.