Skip to content

Releases: haskell/vscode-haskell

1.8.0

06 Dec 15:24
70f6883
Compare
Choose a tag to compare

1.8.0

This release includes some interesting new features:

  • You can now pass custom environment variables to the lsp server
    with the haskell.serverEnvironment config option per project basis,
    thanks to @jacobprudhomme.
    • For example: "haskell.serverEnvironment": { "XDG_CACHE_HOME": "/path/to/my/cache" }
  • With this version the extension will try to use the newer lsp server version
    which supports the ghc used by the project being loaded, thanks to @mduerig
    • WARNING: This will suppose it will use an older version than the latest one,
      without its features and bug fixes.
  • The extension has lot of more log traces now, which hopefully will help to
    identify the cause of issues

What's Changed

New Contributors

Full Changelog: 1.7.1...1.8.0

1.7.1

25 Sep 11:49
67c467e
Compare
Choose a tag to compare

1.7.1

1.7.0

24 Sep 20:08
f2fff2d
Compare
Choose a tag to compare

1.7.0

  • Add an option to set server command line arguments thanks to @cdsmith #464
    • It includes a new config option haskell.serverExtraArgs to being able to pass extra argument to the lsp server executable
  • Update config options to match last haskell-language-server version #463
    • It removes haskell.diagnosticsOnChange and haskell.formatOnImportOn cause they were unused in the server
    • It adds haskell.checkProject, haskell.maxCompletions and haskell.plugin.refineImports.globalOn
  • Fix showDocumentation command thanks to @pranaysashank #452
    • It fixes partially showing the documentation directly in vscode. The documentation is rendered but internal links still does not work
    • Two config options has been added: haskell.openDocumentationInHackage and haskell.openSourceInHackage with default value true
      • So documentation will be opened using the hackage url in an external navigator by default
      • If you prefer having them in vscode you will need to change them to false
  • Create output channel only if there are no existing clients thanks to @pranaysashank #448
    • This fixes the creation of several output channels for the extension

1.6.1

25 Aug 21:50
abd7b6f
Compare
Choose a tag to compare
  • Fix wrapper call to get project ghc version in windows with spaces in path (#439)

1.6.0

08 Aug 09:27
Compare
Choose a tag to compare

1.5.1

04 Aug 12:47
Compare
Choose a tag to compare
  • Add much more logging in the client side, configured with haskell.trace.client
  • Fix error handling of working out project ghc and a bug when the path to the executable contains spaces (See #421)
    • And dont use a shell to spawn the subprocess in non windows systems
    • Show the progress as a cancellable notification
  • Add commands Start Haskell LSP server and Stop Haskell LSP server

1.5.0

03 Aug 10:47
Compare
Choose a tag to compare
  • Emit warning about limited support for ghc-9.x on hls executable download
  • Fix working out project ghc progress notificacion
  • Fix tactics config, thanks to @isovector
  • Update server config to match haskell-language-server-1.3.0 one

1.2.0

11 Oct 17:35
Compare
Choose a tag to compare
  • Add option to open local documentation on Hackage (@DunetsNM)
  • Add haskell.updateBehaviour option to configure when to check for updates
    (@WorldSEnder)
  • Use locally installed servers on connection failure (@WorldSEnder)

1.1.0

19 Aug 11:03
Compare
Choose a tag to compare
  • Add Fourmolu as a plugin formatter provider (@georgefst)
  • Remove the haskell.enable configuration option, since VS Code now allows
    you to disable extensions on a per workspace basis
  • Display errors when fetching from the GitHub API properly

1.0.1

07 Aug 12:05
Compare
Choose a tag to compare
  • Switch the default formatter to Ormolu to match haskell-language-server
  • Fix haskell.serverExecutablePath not working with absolute paths on Windows
    (@winestone)
  • Improve the help text and error message when haskell.serverExecutablePath
    is not found
  • Fix the rendering of the markdown table in the README (@Darren8098)