Start to get a message for the wrong type for LinearGradientProps
See original GitHub issueQuestion
Hello there, starting from today after updating these packages:
I’ve started to get this message
Type '{ children: Element[]; id: string; x1: string; y1: string; x2: string; y2: string; }' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<LinearGradientProps, any, any>> & Readonly<...>'.
Property 'children' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Component<LinearGradientProps, any, any>> & Readonly<...>'.ts(2322)
for every code block, even if I use the example code provided by docs. what happens?
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:10 (2 by maintainers)
Top Results From Across the Web
to get a message for the wrong type for LinearGradientProps ...
Question Hello there, starting from today after updating these packages: I've started to get this message Type '{ children: Element[]; ...
Read more >Failing to alias react-native-linear-gradient to ... - Stack Overflow
by webpack when building the web app. However I am still getting the same error, like its not using the alias. What do...
Read more >LinearGradient - Expo Documentation
Expo is an open-source platform for making universal native apps for Android, iOS, and the web with JavaScript and React.
Read more >react-native-linear-gradient - npm
Invariant Violation: Element type is invalid. Ensure you import the LinearGradient correctly: // Like that: import LinearGradient from ' ...
Read more >react-native-linear-gradient - Bountysource
Hi,. When i pass style props in LinearGradient component, i see typescript is highlighted props error. Later i found that LinearGradientProps does not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@WoLewicki looks like it is fixed! Thanks!
@SamuelAbip can you check if it is fixed in new released v12.4.2 version?