Replies: 6 comments 4 replies
-
I am also a Webstorm user. It seems to be a problem caused by the version upgrade of R3F. Version 8.0.10 did not have this problem. |
Beta Was this translation helpful? Give feedback.
-
I opened a ticket on Webstorm bug tracker that you can like and comment here Basically it can be either solved by R3F by not doing this But they will certainly say "Not my problem, it is your IDE that is not working fine, in VS Code it is working" So basically, we need to pray that Webstorm developers fix this bug, just because R3F is not using a conventional way of declaring the JSX namespace. It's been like already 3 months and no one seems to care. Webstorm on its side is thinking "it happens on just one lib that we don't really care, so it is not a major bug" So as a Webstorm user, we are screwed. So I'm manually declaring a |
Beta Was this translation helpful? Give feedback.
-
My hot fix:
|
Beta Was this translation helpful? Give feedback.
-
I confirm that this was solved in I confirm that the typing works fine in IntelliJ 2023.2 👍 |
Beta Was this translation helpful? Give feedback.
-
My workaround at the moment is to import React in the file I want code completion to work. So just add |
Beta Was this translation helpful? Give feedback.
-
I suffer from the same issue in |
Beta Was this translation helpful? Give feedback.
-
Hi,
The way r3f handles the types in
three-types.d.ts
is not working for Jetbrain's Webstorm completion with typescript.I'm forced to create my own
fiber-types.d.ts
at the root of the project and to copy paste every property of the interface ThreeElements.Do you know any workaround ? I'm new to React ecosystem, so I don't know if it is an issue from r3f or if it is an issue from Webstorm itself. From my researches, I didn't see this way of handling the IntrinsicElements anywhere else.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions