[mmahdi-sz]

Sending a rich message with a media block fails with:

Bad Request: can't parse InputRichBlock: Can't find field "type"

InputRichBlockVideo holds an InputMediaVideo, and that struct has no type field of its own - it normally gets one from the InputMedia enum tag. Inside a block there is no tag, so the media goes out without a type and Telegram rejects it. Same for the photo, animation, audio, voice note and document blocks.

Fixed with a serialize_with that writes the type next to the flattened media. Public API and deserialization are unchanged.

[EdJoPaTo]

Why not something with https://serde.rs/enum-representations.html#internally-tagged ?

This looks overly complex currently with the additional module needed and having that as an enum seems like a better solution? 🤔

[ayrat555]

@mmahdi-sz what do you think about @EdJoPaTo 's suggestion?

[mmahdi-sz]

@ayrat555 @EdJoPaTo

Serde's tag = "type" only works on enums, but here blocks like InputRichBlockPhoto directly hold the concrete InputMediaPhoto struct. Changing that field to an enum breaks backward compatibility and drops compile-time type safety (allows passing audio into a photo block).

That's why #340 went with the exact same serialize_with approach.

I improved my PR and pushed an update to cover all 6 media types in the tests.

[ayrat555]

thank you! merged