-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Duplicate add extension suggestion #380
Comments
Question is whether such a plugin should live in Ghcide or HLS.
Maybe @cocreature could weigh in? |
Seems very similar to the other suggestions we already have in ghcide and it only relies on GHC so I would go for ghcide but I don’t feel all that strongly about this. |
@cocreature - note that this is an existing suggestion, so the question is whether to delete it from Ghcide, or delete it from HLS. |
To fix #555, similar code changes would be applied twice to ghcide and HLS if we maintain the status quo. |
I would say that all ghcide plugins should be separated from the lib, make them follow the haskell plugin definition (introducing hls-plugin-api as dependency) and make ghcide executable depends on those plugins (like we did in hls) That said, that change should be applied as a whole so i would remove the hls plugin in a first step. @berberman so i would fix it in ghcide and delete the hls plugin in one go |
@jneira you should open an issue in the ghcide issue tracker to discuss the extraction of ghcide "plugins". |
I have done this: https://github.com/haskell/ghcide/issues/935 |
Maybe #630 also has the same root? |
So, is this issue still open due to lack of decision to keep/remove Pragma code action from ghcide? |
@gdevanla the plan was remove it from his, any reason to prefer it over ghcide one? |
HLS gives me two quick fixes to add the same LANGUAGE extension:
One of them is coming from the ghcide plugin, the other one's coming from the Pragmas plugin.
Can we turn one off?
Your environment
Steps to reproduce
Screenshot attached
Expected behaviour
I would expect only one suggestion instead of two
Actual behaviour
Seen in the screenshot
The text was updated successfully, but these errors were encountered: