-
-
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
Added basic support for accepting custom shouldForwardProp
option in React Native related packages.
#1642
Conversation
🦋 Changeset is good to goLatest commit: acae230 We got this. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
let mergedProps = pickAssign(testAlwaysTrue, {}, props, { | ||
theme: props.theme || React.useContext(ThemeContext) | ||
}) | ||
let mergedProps = props |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
those changes align the implementation to what we have in @emotion/styled
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 acae230:
|
…n React Native related packages.
2bc12ad
to
acae230
Compare
Codecov Report
|
I'm going to just merge this in as native packages are not our main focus. I'm open to review even after merging - changes are rather trivial though, so 🤷♂ |
…n React Native related packages. (emotion-js#1642)
closes #900
There is an open PR for adding TS types for
@emotion/native
- #1634 - and I'd like to keep those types in sync with what we have for@emotion/styled
and to make it easier I had to implement basic support for this here.