Dexie cloud add() operator sync bug

[NitroRCr]

Reproduction

There is a message object in the table messages
Its contents.0.items was initially an empty array

Execute this:

await db.messages.update('<messageId>', {
  'contents.0.items': add([item])
})

It works fine. The item has been added.

It also triggers sync at the same time, with payload:

Bug when receiving the response:

{
    "changes": [
        {
            "table": "messages",
            "muts": [
                {
                    "type": "update",
                    "keys": [
                        "1idrbrtjc4945r8qqo"
                    ],
                    "changeSpecs": [
                        {
                            "contents": [
                                {
                                    "text": "testttttttttttttttttt",
                                    "type": "user-message",
                                    "items": {
                                        "add": [
                                            {
                                                "id": "1idrc693r4945r9p5h",
                                                "type": "quote",
                                                "name": "用户消息引用 (16)",
                                                "contentText": "sttttttttttttttt"
                                            }
                                        ]
                                    }
                                }
                            ]
                        }
                    ],
                    "txid": "R4ROwJy+lHROKdmK50lbFw=="
                }
            ]
        }
    ],
    "rejections": [],
    // ...
}

The message changed again, and content.0.items became a object with property add:

This is not an expected behavior. I guess it is a bug of dexie-cloud

I'm using [email protected] and [email protected]

[onuradsay]

I think this is the same problem with #2113

[dfahlander]

Fixed in latest dexie and dexie-cloud-addon:

[email protected]
[email protected]