Skip to content

hls-plugin-api: version bump #405

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

Closed
wants to merge 1 commit into from
Closed

Conversation

Galagora
Copy link

@Galagora Galagora commented Sep 16, 2020

The version on Hackage currently doesn't build. This prevents the current master from being built in Nixpkgs. @alanz, please upload the 0.4.0.1 tarball to Hackage.

--- Version on Hackage
+++ Master version
@@ -39,7 +39,7 @@

 commandAddSignature :: CommandFunction WorkspaceEdit
 commandAddSignature lf ide params
-    = executeAddSignatureCommand lf ide (ExecuteCommandParams "typesignature.add" (Just (List [toJSON params])) Nothing)
+    = commandHandler lf ide (ExecuteCommandParams "typesignature.add" (Just (List [toJSON params])) Nothing)

 -- ---------------------------------------------------------------------

@jneira jneira linked an issue Sep 16, 2020 that may be closed by this pull request
@jneira
Copy link
Member

jneira commented Sep 16, 2020

But the actual ghcide released version (0.3.0) does not have commandHandler in https://github.com/haskell/ghcide/blob/v0.3.0/src/Development/IDE/Plugin/CodeAction.hs, but executeAddSignatureCommand.
Afaiu we should wait to the next ghcide release to upload this change to hackage.
So the nix build is not using ghcide from hackage but it does for hls-plugin-api?

@Galagora
Copy link
Author

Galagora commented Sep 16, 2020

@jneira
Copy link
Member

jneira commented Sep 16, 2020

Aha, i am afraid that still we'll have to wait to a ghcide release or cabal get hls-plugin-api && cd hls-plugin-api && cabal build will fail, and the projects using hls-plugin-api directly from hackage will do too.
I am not a nix expert but, could the nix build use the hls-plugin-api from the hls repo instead from hackage? It will be make the build more robust

@jneira
Copy link
Member

jneira commented Sep 16, 2020

Well, i am afraid that the hackage version of hls-plugin-api cant be built standalone cause it relies in the ghcide fork that was used when it was uploaded. It fails to compile with the hackage version of ghcide 😟
That should not be like that, and i still think the next release should be done correctly, against a suitable released ghcide version.

@alanz
Copy link
Collaborator

alanz commented Sep 16, 2020

The package was published in a rush to enable a munihac workshop. So the release admin was not very good, sorry, my fault.

@Galagora
Copy link
Author

I agree; it's more robust to use the hls-plugin-api from this repo, rather than from Hackage.

@Galagora Galagora closed this Sep 16, 2020
pepeiborra pushed a commit that referenced this pull request Dec 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants