Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Current from HapticFeedback #6802

Merged
merged 1 commit into from
May 4, 2022
Merged

Remove Current from HapticFeedback #6802

merged 1 commit into from
May 4, 2022

Conversation

jfversluis
Copy link
Member

Description of Change

Removes the Current property from HapticFeedback as it seemed redundant and Default made the most sense in this context

Issues Fixed

Fixes #6799

@jfversluis jfversluis added the area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info label May 4, 2022
@jfversluis jfversluis requested a review from mattleibow May 4, 2022 07:42
@jfversluis
Copy link
Member Author

@mattleibow was there a specific reason both were on here?

@Redth Redth merged commit 2634172 into main May 4, 2022
@Redth Redth deleted the haptic-remove-current branch May 4, 2022 15:11
@mattleibow
Copy link
Member

No reason, just a stack of copy paste I think

@github-actions github-actions bot locked and limited conversation to collaborators Dec 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-essentials Essentials: Device, Display, Connectivity, Secure Storage, Sensors, App Info
Projects
None yet
Development

Successfully merging this pull request may close these issues.

What is the difference between HapticFeedback.Current and .Default?
4 participants