Fix deprecation warnings

[nohli]

During every Android build flutter_vibrate triggers a warning about deprecation.

See void vibrate() on https://developer.android.com/reference/android/os/Vibrator

https://stackoverflow.com/questions/45605083/android-vibrate-is-deprecated-how-to-use-vibrationeffect-in-android-api-26

[nohli]

@rodydavis did you stop maintaining this package?
Maybe someone can help you here as a contributor, or fork the GitHub repo (preferably with enabled issues), and re-publish a new package to pub.dev?
What do you think?

[rodydavis]

I don’t maintain the vibrate plugin, this is a fork but I’m open to fixes

[rodydavis]

I.e. I don’t maintain vibrate, but I do flutter_vibrate

[rodydavis]

Will publish soon

[nohli]

@rodydavis I meant flutter_vibrate.

A null safe version without deprecation warnings will be perfect, thanks a lot! 😊

Btw.
Is there a reason why you disabled issues?
As far as I understand, this fork is the repo for flutter_vibrate on pub.dev (so it could have an issue tracker).

[rodydavis]

I didn’t disable it, but I don’t think I never enabled it. This was originally forked and added haptic feedback when I first did it. I will publish it and turn on issues soon, I’m going through all my packages and upgrading and doing maintenance. But almost through!

[nohli]

@rodydavis please don't forget us 😛

Thanks for all your work for the community 🙂

[rodydavis]

Published! 1.1.0