Skip to content

Commit 8687376

Browse files
committed
readme update
1 parent f472d56 commit 8687376

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,9 @@
77

88
### Android Permissions with Kotlin Coroutines and Flow API
99

10-
No more callbacks, builders, listeners or verbose code for requesting Android permissions.
11-
Get Permission Request Result with one function call.
10+
No more callbacks, listeners or verbose code for requesting Android permissions.
11+
Get Permission Request Result asynchronously with one function call.
12+
`Context` or `Activity` not needed for requests, request permissions from your View Model or Presenter.
1213
Built with [Kotlin Coroutines](https://github.com/Kotlin/kotlinx.coroutines)
1314
and [Flow](https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines.flow/-flow/).
1415
***
@@ -67,7 +68,7 @@ val granted: Boolean = requester.areGranted(Manifest.permission.CAMERA, Manifest
6768

6869
### Why Flows?
6970

70-
Requesting multiple permissions in a single go represents a data stream of `PermissionsResult` objects. `Flow` fits here
71+
Requesting multiple permissions in a single request represents a data stream of `PermissionsResult` objects. `Flow` fits here
7172
perfectly. Each permission requested is either granted or denied, with `Flow` we can operate on each emitted result item
7273
and inspect it individually, that is check if it is Granted, Denied or Needs Rationale. Flows are async and require a
7374
coroutine to collect so this is not a huge update from Peko version 2. Also, they are now part of Kotlin Coroutines

0 commit comments

Comments
 (0)