- Added dismiss functionality regarding issue 140

[GerasimosGots]

• Added functionality for dismissing the spinner when the default dismiss spinner does not work, through view hierarchy #issue_140

Guidelines

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

This commit is regarding issue 140 that I have already opened, It's a suggested solution to the problem that I mentioned. I already use it in my project with success, so I thought we can add it as an extra helping functionality in PowerSpinner library.

The problem was that in some cases the power spinner stays visible and cannot be dismissed.
My proposed solution is an extension function of the parent view, that iterates all the view hierarchy of the current view,
if we find an instance of PowerSpinner view then dismiss it (with the already dismiss functionality).

• Added two extension functions in PowerSpinnerExtension file, one public and the other private.
• Added some comments for each function

The usage is fairly easy -> parentView?.dismissPowerSpinner()

Types of changes

What types of changes does your code introduce?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Preparing a pull request for review

Ensure your change is properly formatted by running:

$ ./gradlew spotlessApply

Please correct any failures before requesting a review.

[skydoves]

Looks perfect! 💯
Thank you for your contribution :)

[skydoves]

Hey @GerasimosGots, before merging this, could you run ./gradlew spotlessApply and ./gradlew apiDump command lines?

[GerasimosGots]

Hey @GerasimosGots, before merging this, could you run ./gradlew spotlessApply and ./gradlew apiDump command lines?

Done!