Closed HarmonicPool closed 1 year ago
Your logs from the vscode-haskell issue indicate that nix sets up HLS 1.5.1.0, which is outdated.
Well that's unfortunate since I should be using the last release
Is there something I'm doing wrong, or that I can do inorder to get the haskel-language-server v1.7.0.0?
Well, I have no investment in nix. I've never used plutus-apps with it. But I've developed smart contracts with just using cabal. That should work fine with the appropriate cabal.project
. I usually follow https://github.com/input-output-hk/plutus-starter/blob/main/cabal.project
Well, I have no investment in nix. I've never used plutus-apps with it. But I've developed smart contracts with just using cabal. That should work fine with the appropriate
cabal.project
. I usually follow https://github.com/input-output-hk/plutus-starter/blob/main/cabal.project
setting up the project without ``nix``` solves the problem
hm, I don't have this issue with hls 1.5.1, nix and vscode. Did hls have the time to compile everything? there is progress status in the bottom stripe in vscode. Also maybe there is a compile issue earlier? As one can often get plutus-tx plugin errors (GHC Core to PLC plugin error).
yes I have lots of "GHC Core to PLC plugin error" and I have all the GHC-options specified in the plutus docs > troubleshooting > plugin errors
onestly I got used to them since when running cabal repl
or cabal buld
everything goes fine and any other error is showed with more priority in vscode
hls
is compiled since I can use it by hand in the shell
We have switched to nix develop
with newer versions of hls. Please re-open if there will be any problems with it.
@ak3n can you elaborate?
Summary
I can't get to work with the
hls
features while writing plutus as mentioned in the VSCode repository issueSteps to reproduce the behavior
then in the generated environment:
Actual Result
the extension doesn't work
Expected Result
the generated environment allows me to work using the
haskell-language-server
featuresDescribe the approach you would take to fix this
see this issue
System info
lsb_release -a