From 5b83d5a151eedfb5057643b61c65426c62423d75 Mon Sep 17 00:00:00 2001 From: hotchemi Date: Sun, 30 Dec 2018 19:03:19 +0900 Subject: [PATCH] Update readme. --- doc/java_usage.md | 2 +- doc/kotlin_usage.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/java_usage.md b/doc/java_usage.md index 08ca525f..69b4c17f 100644 --- a/doc/java_usage.md +++ b/doc/java_usage.md @@ -16,7 +16,7 @@ PermissionsDispatcher introduces only a few annotations, keeping its general API |Annotation|Required|Description| |---|---|---| -|`@RuntimePermissions`|**✓**|Register an `Activity` or `Fragment`(we support both) to handle permissions| +|`@RuntimePermissions`|**✓**|Register an `Activity`, `Fragment` or [Controller](https://github.com/bluelinelabs/Conductor) to handle permissions| |`@NeedsPermission`|**✓**|Annotate a method which performs the action that requires one or more permissions| |`@OnShowRationale`||Annotate a method which explains why the permissions are needed. It passes in a `PermissionRequest` object which can be used to continue or abort the current permission request upon user input. If you don't specify any argument for the method compiler will generate `process${NeedsPermissionMethodName}ProcessRequest` and `cancel${NeedsPermissionMethodName}ProcessRequest`. You can use those methods in place of `PermissionRequest`(ex: with `DialogFragment`)| |`@OnPermissionDenied`||Annotate a method which is invoked if the user doesn't grant the permissions| diff --git a/doc/kotlin_usage.md b/doc/kotlin_usage.md index fafe8b75..d5cf0037 100644 --- a/doc/kotlin_usage.md +++ b/doc/kotlin_usage.md @@ -16,7 +16,7 @@ PermissionsDispatcher introduces only a few annotations, keeping its general API |Annotation|Required|Description| |---|---|---| -|`@RuntimePermissions`|**✓**|Register an `Activity` or `Fragment`(we support both) to handle permissions| +|`@RuntimePermissions`|**✓**|Register an `Activity`, `Fragment` or [Controller](https://github.com/bluelinelabs/Conductor) to handle permissions| |`@NeedsPermission`|**✓**|Annotate a method which performs the action that requires one or more permissions| |`@OnShowRationale`||Annotate a method which explains why the permissions are needed. It passes in a `PermissionRequest` object which can be used to continue or abort the current permission request upon user input. If you don't specify any argument for the method compiler will generate `process${NeedsPermissionMethodName}ProcessRequest` and `cancel${NeedsPermissionMethodName}ProcessRequest`. You can use those methods in place of `PermissionRequest`(ex: with `DialogFragment`)| |`@OnPermissionDenied`||Annotate a method which is invoked if the user doesn't grant the permissions|