Vandolf Estrellado
Vandolf Estrellado
Add option to apply offset and limit manually in all query APIs for devices that do not support them
This is something that I considered in #243 but did not implement yet because no one wanted it until #252 (thanks to @itinsidenews) ## Problem As discovered in issue #241...
Currently, the `AccountsLocalRawContactsUpdate` API allows library users to move **local RawContacts to an Account** because the default Android Open Source Project (AOSP) Contacts app supports it. However, I recently started...
The native Contacts app (or AOSP Contacts) parses a bunch of xml files coming in from other apps that declare their custom data in xml. This allows external apps to...
Wait for #167 before working on this. - [ ] Create label - [ ] Update label - [ ] Delete label
Requires https://github.com/vestrel00/contacts-android/issues/25
Enables import existing contacts from and export to .VCF file. Additionally, new (raw) contacts (not in the database) or existing (raw) contacts with unsaved changes will be exportable. Consumers will...
In similar nature to #119, we should refactor the extension functions defined in `contacts.core.util.ContactOptions` and `contacts.core.util.RawContactOptions`. Then, add a way to set/remove options as part of insert and Update APIs....
Currently, the library provides no functions to check if the main SIM card is ready for read/write operations. Such functions are important for users of this library. Also, it is...
[Dexter](https://github.com/Karumi/Dexter), sadly, is now archived. To give consumers confidence in this actively maintained library, we need to move away from Dexter. Also, replacing Dexter **may** resolve #143. Think about other...
Currently, the library has artificially placed some "Account restrictions" on certain entities. - Insert and update operations for these data kinds of a local RawContact (not associated with an Account)...