feat: support RN 0.62 accessibilityState in toBeDisabled #30
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
Codecov Report
@@ Coverage Diff @@
## master #30 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 8 8
Lines 90 92 +2
Branches 24 24
=========================================
+ Hits 90 92 +2
Continue to review full report at Codecov.
|
MichaelDeBoey
requested changes
Jul 25, 2020
|
🎉 This PR is included in version 3.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
What:
This PR adds support to the prop
accessibilityStateto the matchertoBeDisabledWhy:
RN 0.62 removed the old prop
accessibilityStatesin favor ofaccessibilityStatehttps://reactnative.dev/blog/2020/03/26/version-0.62#breaking-changes
How:
I created a new condition
hasStateDisabledto verify whether the propaccessibilityStatehas disabled in its value to be used together with the old condition foraccessibilityStates. Maybe in the future, we can deprecate and remove this.Checklist: