Skip to content
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

Closed
pepeiborra opened this issue Sep 6, 2020 · 12 comments
Closed

Duplicate add extension suggestion #380

pepeiborra opened this issue Sep 6, 2020 · 12 comments
Labels
component: ghcide component: plugins status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet type: enhancement New feature or request

Comments

@pepeiborra
Copy link
Collaborator

HLS gives me two quick fixes to add the same LANGUAGE extension:

image

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

  • HLS 0.4.0 head
  • VS Code
  • HLS codebase using the default cradle (Cabal I think)

Steps to reproduce

Screenshot attached

Expected behaviour

I would expect only one suggestion instead of two

Actual behaviour

Seen in the screenshot

@ndmitchell
Copy link
Collaborator

Question is whether such a plugin should live in Ghcide or HLS.

  • DAML probably wants it, suggesting Ghcide.
  • Makes Ghcide a standalone usable IDE, although I'm not sure that's something we want to aim for.
  • Generally decoupling whatever we can is as best as possible, suggesting HLS.

Maybe @cocreature could weigh in?

@cocreature
Copy link
Contributor

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.

@ndmitchell
Copy link
Collaborator

@cocreature - note that this is an existing suggestion, so the question is whether to delete it from Ghcide, or delete it from HLS.

@Ailrun Ailrun added the status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet label Sep 8, 2020
@berberman
Copy link
Collaborator

To fix #555, similar code changes would be applied twice to ghcide and HLS if we maintain the status quo.

@jneira
Copy link
Member

jneira commented Nov 6, 2020

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)
I would keep them in the ghcide repo to make them available to daml, that maybe would need be refactored to acommodate that change (not sure about that)

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

@pepeiborra
Copy link
Collaborator Author

@jneira you should open an issue in the ghcide issue tracker to discuss the extraction of ghcide "plugins".

@pepeiborra
Copy link
Collaborator Author

@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
https://github.com/haskell/ghcide/issues/936

@Ailrun
Copy link
Member

Ailrun commented Dec 6, 2020

Maybe #630 also has the same root?

@gdevanla
Copy link
Contributor

So, is this issue still open due to lack of decision to keep/remove Pragma code action from ghcide?

@jneira
Copy link
Member

jneira commented Dec 10, 2020

@gdevanla the plan was remove it from his, any reason to prefer it over ghcide one?
And yeah there is no technical reason to wait for do it so a pr would be very welcomed

@jneira
Copy link
Member

jneira commented Dec 10, 2020

@gdevanla sorry, i had not seen your pr (#662) that seems to be related. So if the hls plugin is more complete thanks to it, it would be a good reason to keep it and delete ghcide one

@jneira
Copy link
Member

jneira commented Jan 12, 2021

Afaik this one was closed by #948, thanks @gdevanla!

@jneira jneira closed this as completed Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ghcide component: plugins status: in discussion Not actionable, because discussion is still ongoing or there's no decision yet type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants