Opposite merge flag meaning for Batch.Set and Transaction.Set method in Android Wrapper

[weinamdev]

Hi there,

I found the merge flag for Set method in both Transaction and Batch in Android wrapper carry opposite meaning as compared to Document.SetAsync, which is consistent with Firebase official documentations.

However, Batch.Set and Transaction.Set in iOS wrapper working fine, and performing consistently with Document.SetAsync definition.

Expected Behavior: When Merge = true, only replace the affected fields

Actual Behavior: In Android Wrapper, Merge flag in batch write and transaction works in opposite way, hence when Merge = false only replaces affected field, and Merge = true replace the entire document

Thank you.

[ccgould]

Surprised this hasn't been fixed yet.