Update documentation and get rid of serialize-only Message type #23

leftmostcat · 2024-10-28T21:04:12Z

This proposes a series of updates to Toby's PR at #18 to more rapidly illustrate what I'm expecting.

src/types/common.rs

src/types/create_item.rs

src/types/update_item.rs

src/types/create_item.rs

tobypilling

Very nice. Love this forward thinking on the other uses for Updates

* Created UpdateItem and added necessary trait implementations * Respond to feedback on UpdateItem, unduplicate MessageDisposition (now as Option<MessageDisposition>) and add Clone for all types * Also added default trait for ConflictResolution * Adjusted comment to use a noun phrase for ConflictResolution * Fixed formatting issues * Test formatting * Fix formatting again * Test broken formatting * Test broken formatting * Fix broken formatting * Update documentation and get rid of serialize-only Message type (#23) * Add reference to EWS updateitem docs --------- Co-authored-by: Sean Burke <[email protected]>

#23 updated CreateItem to use the same Message type for both serialization and deserialization. However, it did not add the attributes that xml-struct-rs uses to correctly include the prefix for the t/types namespace on relevant tags. This change updates all of the fields under Message, so future developments aren't bitten by this error. According to https://learn.microsoft.com/en-us/exchange/client-developer/web-service-reference/createitem-operation-email-message#createitem-request-example, both the Message and its children need the t prefix.

Update documentation and get rid of serialize-only Message type

2a786e8