-
-
Notifications
You must be signed in to change notification settings - Fork 390
Imports are not suggested anymore #2013
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
Comments
Hi, thanks for the bug report. could we have a reproduction case (a link to a github project would be nice for example)? |
Hi @jneira, I don't know if this will be useful for you, but I am using a Mac and I also have this issue. Just adding a few files to make the 2nd homework from CIS194: https://www.seas.upenn.edu/~cis194/spring13/lectures.html, you can see that there is no imports suggestion, nor for own functions nor for externals: Hope it will be useful. Regards, Kozaky |
thanks for the additional info, I've observed hls suggest disable |
I'm very sorry, I didn't notice the reply in time. The particular quick action (suggesting an import) stopped showing up for all of my projects, including new ones, generated by When the extensions starts, it puts out the following logs:
(etc etc) When I add an import myself (an import I wished would be suggested), I can hover over the imported symbols and see the documentation and the type just fine. All the other features seem to work fine, except:
|
I can reproduce this with GHC 9.4.2 but not with 8.10.7. Both use HLS 1.8.0.0: https://github.com/aavogt/import-code-action |
For GHC 9.4.2, the plugin which takes care of imports is not enabled yet, afaict. |
Closing as old and quiet |
Somehow imports are not suggested to me anymore, as they used to be. Which is really sad, it was a great feature:
I've looked all over the plugin settings and the logs. hls correctly determines stack, and it's just a normal stack. Everything works, except those import suggestions. I miss them. What can I do to get them back? Thank you!
The text was updated successfully, but these errors were encountered: