You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #342 with @Yameteh, some OEMs such as Oppo and its ColorOS allows a RawContact to have multiple Notes.
The CRUD APIs provided in this library currently only supports one Note per RawContact. Currently,
only one Note is read per RawContact even if there are more than one in the Data table
performing an update operation on a RawContact with multiple existing Notes may result in unexpected behavior such as update not working or even all Notes being deleted except for one
The behavioral contract that has been upheld by many different OEMs for Notes is that a RawContact only has a single Note. The following OEMs adheres to this implicit contract;
Google
Samsung
Xiaomi / Redmi
RedMagic
Lenovo (ZUI)
Apple (iOS)
Solution
Add support for multiple Notes per RawContact.
This must be an opt-in feature / behavioral change.
Do not change the existing API contract of one Note per RawContact.
Create extension functions instead.
This solution requires #344 to be implemented first.
Update Kotlin docs
Update markdown docs
Update gh-pages
The text was updated successfully, but these errors were encountered:
Problem
As discussed in #342 with @Yameteh, some OEMs such as Oppo and its ColorOS allows a RawContact to have multiple Notes.
The CRUD APIs provided in this library currently only supports one Note per RawContact. Currently,
The behavioral contract that has been upheld by many different OEMs for Notes is that a RawContact only has a single Note. The following OEMs adheres to this implicit contract;
Solution
Add support for multiple Notes per RawContact.
This solution requires #344 to be implemented first.
gh-pages
The text was updated successfully, but these errors were encountered: