-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add pressable native component #1958
Add pressable native component #1958
Conversation
💥 No ChangesetLatest commit: e5cbd14 Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂 If these changes should be published to npm, you need to add a changeset. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Click here to learn what changesets are, and how to add one. Click here if you're a maintainer who wants to add a changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit e5cbd14:
|
guess this will require a bump of the |
I have done this recently on another branch - so don't worry about it.
Yes, as we are publishing prereleases from this |
Codecov Report
|
…on-js#1958) * add Pressable component to native types * add new Pressable component to @emotion/native * Remove ReactNativeComponentNames and simplify typings in the result Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
What: Add support for the new Pressable component introducted in React Native 0.63 https://reactnative.dev/blog/2020/07/06/version-0.63#pressable
Why: Without these changes users are unable to use
styled.Pressable
to create Pressable components.How: Added Pressable to the components array in the code and added it to the ReactNativeComponentNames union type.
Checklist:
Not sure if I should run
yarn changeset
seeing as this would go intonext
?