-
Notifications
You must be signed in to change notification settings - Fork 74
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
goToDefination not working in WebStorm #262
Comments
Hi, also have the same issue. |
Hi there, I haven't tried this in WebStorm (only VS Code), but the way this works is that it "tricks" TypeScript into thinking the CSS is a declaration file (in memory), so it "should" work wherever the plugin itself works. The PR you linked to might solve the issue, but I can't guarantee it... I will try to look at that soon. |
Thank you, I hope you find a solution :) I would also be very grateful if you could check your solution in Webstorm and try to find out why it doesn’t work there. |
Perhaps there is a similar setting, but for the Webstorm configuration? { |
Hi there, @mrmckeb i tried use fork of @astrodelete PR's as local deps and i still have problem describe early :( |
Hi all, I've reviewed the docs for WebStorm again today and wondered if this is the missing setting? |
Hi, hope we can resolve this issue
I use WebStorm 2023.2.4
When i import my styles object, it has correct types
Autocomplete working well, i can write selectors
But when i try to go to defination i gor error in webstorm
I also tried goToDefination in VSCode, with
And in this case working fine
What can i do for correct work in WebStorm?
The text was updated successfully, but these errors were encountered: