Bug: Array fields are not supported in Supabase replication (push fails with "unknown how to handle type: object")

[len360]

Description

When using Supabase replication, documents containing array fields (e.g. string[]) cause the push process to fail with the following error:

Error: unknown how to handle type: object

This issue occurs during update (patch) and delete operations, while insert operations work correctly.

---

Steps to reproduce

1. Define a schema with an array field:

{
	"title": "hero schema",
	"version": 0,
	"primaryKey": "name",
	"type": "object",
	"properties": {
		"name": {
			"type": "string",
			"maxLength": 100
		},
		"skills": {
			"type": "array",
			items: { type: "string" }
		}
	}
}

2. Insert a document:

await collection.insert({
  name: "Foo",
  skills: ["Teaching", "Summarizing"],
});

3. Run replication

4. Delete the document:

await doc.remove();

5. Trigger replication

---

Location of the Issue

The issue appears to originate from the addDocEqualityToQuery function, where document fields are converted into query filters.

export function addDocEqualityToQuery<RxDocType>(
    jsonSchema: RxJsonSchema<RxDocumentData<RxDocType>>,
    deletedField: string,
    modifiedField: string,
    doc: WithDeleted<RxDocType>,
    query: any
) {
	// ....
	
	for (const key of Object.keys(doc)) {
        if (ignoreKeys.has(key)) {
            continue;
        }

        const v = (doc as any)[key];
        const type = typeof v;

        if (type === "string" || type === "number") {
            query = query.eq(key, v);
        } else if (type === "boolean" || v === null) {
            query = query.is(key, v);
        } else if (type === 'undefined') {
            query = query.is(key, null);
        } else {
            // Problem: arrays and JSON objects are not handled
            throw new Error(`unknown how to handle type: ${type}`)
        }
    }
    
    //...
}

[pubkey]

Can you make a PR with a test case that reproduces your problem?
You can start with this template.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag.

[mindofjonas]

@pubkey I see this marked as completed but looks like the changes never landed on main and weren't released. Ran into this issue locally and I'm currently running a patched version of the plugin as a work-around.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag.