Apply Option difference to `None` target doesn't work as expected

[User-TGK]

Example to reproduce the issue

use serde::{Deserialize, Serialize};
use serde_diff::{Apply, Diff, SerdeDiff};

#[derive(SerdeDiff, Serialize, Deserialize, PartialEq, Debug, Clone)]
struct TestStruct {
    a: Option<i32>,
}

fn main() {
    let old = TestStruct { a: Some(5) };
    let new = TestStruct { a: Some(10) };
    let mut target = TestStruct { a: None };
    let expected = new.clone();

    let diff = Diff::serializable(&old, &new);
    let json_diff = serde_json::to_string(&diff).unwrap();
    let mut deserializer = serde_json::Deserializer::from_str(&json_diff);

    Apply::apply(&mut deserializer, &mut target).unwrap();

    assert_eq!(target, expected);
}

Expected result

For target to equal TestStruct { a: Some(10) }

Actual result

Target equals TestStruct { a: None }

[Boscop]

@kabergstrom Any idea why that could be?
If both are Some, their contents are compared here:

serde-diff/src/implementation.rs

Line 345 in e461da4

if <T as SerdeDiff>::diff(self_item, ctx, other_item)? {

[Boscop]

@User-TGK Actually, I think you're applying it wrongly (@kabergstrom Correct me if I'm wrong):
SerdeDiff assumes that the target you're applying the diff to is equal to the old value that was used to compute the diff. (In other words, the computed diff is only valid to be applied to an object that is equal to the old value it was computed from.)
So you should assert that the diff applied to old equals new.

I ran into a similar issue here: #16 (comment)
In my use case I'm sending diffs over websockets.
I solved that issue by resetting the client's copy of the state to Default::default() upon reconnect (because while the client was disconnected, its instance of the state went out of sync with the server's instance, which would make the next diff invalid to be applied to the client's instance), and then the server sends diff(Default::default(), current) to the client right after reconnect, before any other msgs.
Let me know if you find a better workaround :)

[User-TGK]

Thanks for the info @Boscop. The workaround I currently use is replacing the following line with the snippet below.

serde-diff/src/implementation.rs

Line 383 in e461da4

ctx.skip_value(seq)?;

    if let Value(v) = ctx
        .read_next_command(seq)?
        .expect("Expected value")
    {
        changed = true;
        *self = Some(v);
    }

I didn't look into the implementation details of the library so I am not sure whether this will cause issues, but it does the trick for now.