Extension for running blocks with permissions in an Activity about android-ktx

[scottroemeschke]

Things like permissions, and other complex APIs (Fingerprint is another good example) may not be right for this library.

You could redesign permissions API essentially in Kotlin in 10 different ways, (for instance a sealed class PermissionsResult type or a bunch of callback-lamdas you pass in) all of them Kotlin-y and simpler than existing API.

And it might even be a "better" API for the average dev.

But it would be rather opinionated, and heavy. And lots of methods/classes etc wrapping the functionality.

Not sure if those sorts of things are the goal for android-ktx or should be separate libraries. I would think the goal would be relatively non-opinionated straightforward extensions/functions (not API redesigns)

[kevinmost]

If it's going to be vararg, wouldn't it be useful to know which permissions are granted or not? If there's going to be an extension to handle this, as well, would it be useful to know if a rationale should be shown (ie, if the user declined the permission just once or permanently)?

[davethomas11]

Yes perhaps being returned the boolean plus information would be helpful. I'd ignore the permissions which are being granted in most cases, and just care that they were all present for the action I want to execute.

I'm ok with handling rationale outside of the extension beforehand if needed.

[JakeWharton]

I have a hard time seeing how this could work. It seems like a much better target for coroutines where the suspending nature of a function could be made apparent. The suggested approach does not convey the asynchronous nature of the block nor provides a mechanism for stopping the operation.

[davethomas11]

@scottmeschke I agree with the sentiment, not a good fit for this library.