refactor(haptics): remove cordova haptics support #29186
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liamdebeasi
requested review from
thetaPC and
a team
and removed request for
a team
sean-perkins
approved these changes
Mar 20, 2024
|
According to https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#type, we use |
|
I guess even conventional commits doesn't have a specification around removing features. I'm ok with refactor. My main concern was visibility in the CHANGELOG for developers to know this support has been removed. It's included in the breaking changes, so I think that concern is covered. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: Internal
What is the current behavior?
Ionic Framework relies on the haptics plugin for certain interactions such as spinning the Picker or dragging the knob on a Toggle. Up until now we have had support for both Cordova and Capacitor haptics plugins. As a result of a previous incident, the team wanted to investigate dropping support for the Cordova haptics plugin in favor of pushing developers to migrate to Capacitor.
What is the new behavior?
Does this introduce a breaking change?
Other information