I would like to see a method that lets the developer to attach a permission to a specifc slide via tags.

Can you clarify what is a TAG in this context?

I got it from your PR, thanks for submitting it. I think this change is quite invasive and I'm unsure we want to offer it.

Invasive? Its a relatively small change, that doesnt even affect existing installations, what problems do you see for the future with this? Is there something i could improve?

You're basically introducing a new concept (the 'tag') for all the users, that is needed only for a specific feature. I'd rather find a different approach.

For example, something like this overload:

askForPermissions(Array<String>, Fragment, Boolean)

would work better imho

The tag itself is entirely optional, but i see the point that it might make the change bigger than it needs to be. Though implementing your Fragment argument might require a huge change to the code to fit it into the permissionMap without breaking the existing slideNumbers.

However, another addition to attaching permissions to a specific slide would be, that it makes recognizing a specific slide more easy.

As an eyample, to request storage permissions i have to write custom code and call that. To do so, i need to check on which slide i am, and on what slide i am supposed to make the request. I have to keep track of the slideNumbers again. With a tag, i can just check wether or not i am on my target slide.

On the other hand, i will have to check if it is possible to archieve the same with a reference to the fragment itself as you proposed.

@cortinico

I have updated the PR to accept a fragment:

        // Here we ask for camera permission on slide 2
        askForPermissions(arrayOf(Manifest.permission.CAMERA), 2)

        // Here we ask for Location permission on slide 4
        askForPermissions(arrayOf(Manifest.permission.ACCESS_FINE_LOCATION), "yourCoolId")

        // Here we ask for Calendar permission on slide 5
        askForPermissions(arrayOf(Manifest.permission.READ_CALENDAR), calendarPermissionFragment)

The tag is now an id, and a property of AppIntroFragment (AppIntroFragment.slideId)
I have still exposed the ability to expose the id to the user, because the logic i use is basically the same. If a fragment is passed to the askForPermission function, the slideId is used to identify the permission in the map. If it is specifically set by the dev, it is used as-is, but if none was set i generate a UUID on the fly so that the id is not a requirement anymore. Though i think it really could be useful to identify specific slides easily.