Closed hotchemi closed 5 years ago
I'm a little sad to let go of the PermissionRequest
interface, because I liked the straightforwardness of calling proceed()
and cancel()
directly. Usually, our generated class names are quite long, so this introduces two more instances where we utilize long calls.
What do you think about keeping both? I mean, the PermissionRequest
could still keep its simple API, and we still generate the additional static methods, to which the request would delegate. This is the best of both worlds, however it does raise the complexity of the generated code, since @OnShowRationale
's parameter would become optional...
Ooh your proposal seems better:D I didn't come up with that somehow but then we can avoid loosing backward compatibility! @mannodermaus
Let me create another PR since the diff is so huge .
Issue
resolves https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/434
Overview
This API change is based on https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/434#issuecomment-447257123 discussion.
1. Attach annotations
2. Delegate to generated functions