-
Notifications
You must be signed in to change notification settings - Fork 614
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
11.5.1 or newer TypeScript issue with styled components #381
Comments
I'm not familiar with styled-components in react-native. Could it be because we need to expose the "style" prop in the TS interface? |
Not sure exactly what is the reason, but it has to do with the typings of |
@rewieer I'm wondering why you're closing this. |
Why is this closed? This issue is still happening |
I'm also getting this error... |
Workaround for now (the styles are applying to the Modal):
This error should be fix tho as it might introduce some bugs |
@aldebout having no feedbacks since December I archived it. Since it pops up, i'm going to reopen it. |
I'm also getting this error...
This works. |
The error still exists. Used the |
Persists on
|
still on |
Still on |
still on
|
Still on |
1 similar comment
Still on |
🎉 This issue has been resolved in version 13.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
## [13.0.1](react-native-modal/react-native-modal@v13.0.0...v13.0.1) (2022-03-01) ### Bug Fixes * make getDerivedStateFromProps's nextProps param Readonly ([#647](react-native-modal/react-native-modal#647)) ([c737e7f](react-native-modal/react-native-modal@c737e7f)), closes [#381](react-native-modal/react-native-modal#381)
This seems to be an issue with newer versions of TypeScript and/or styled-components. |
Versions
Description
I see in change log was add TypeScript support. I use styled components and started get next error here:
The text was updated successfully, but these errors were encountered: