Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add extensions for checking the value of ContactsContract.DataColumns.IS_READ_ONLY for any ExistingDataEntity #307

Closed
4 tasks done
vestrel00 opened this issue Sep 1, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@vestrel00
Copy link
Owner

vestrel00 commented Sep 1, 2023

Problem

As discussed in #301 an in #306, including the IS_READ_ONLY column in the projection array of queries result in an exception being thrown. This means that we are unable to read the value of it and in turn we are unable to add the isReadOnly property to the more generalized DataEntity...

Solution

Since it is possible to refer to the column in selection/WHERE clause of queries, we can at least provide an extension function to check its value.

  • Create async module functions.
  • Update relevant in-code documentation.
  • Update relevant docs (about-api-entities.md, convenience-functions.md)
  • Update gh-page branch
@vestrel00
Copy link
Owner Author

🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥
This is now release in 0.3.1!
🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant