hie-bios
hie-bios copied to clipboard
haskell
Set up a GHC API session for various Haskell Projects
PR for https://github.com/haskell/haskell-language-server/pull/2994. I am just creating the PR to see what changes are necessary.
Apparently I messed this up since https://github.com/haskell/hie-bios/pull/330, which means CI didn't run any bios tests since about six months. So we either can applaud ourselves for testing locally, or some...
Add parser tests for non-standard `cabal.project` file locations Add bios tests for projects with non-standard `cabal.project` file locations Follows the same structure as `stackYaml` feature for stack cradles. Fixes #263
Introduce API changes necessary for #301 This PR can be merged before #301, and released, then HLS can be updated for the new API.
In a project I use, we have a build-type: Custom. During executing Setup.hs, a new .hs file is being generated. Currently, I use the HSL setup with VSCode. That works...
That's just to document how to silence Multi Cradle for `Setup.hs` files. See the solution [here](https://github.com/haskell/haskell-ide-engine/issues/1650#issuecomment-650192055). `hie.yaml` can initially be generated by [implicit-hie](https://github.com/Avi-D-coder/implicit-hie#readme).
> Until now, we threw an error message. The point being that you notice you didn't write the correct configuration and something is not right. This will make it hard...
### Context At work we use stack with HLS. But we also use stack to run our application/tests. By default HLS will build things into the same stack workdir as...
* Like we added `stack-yaml` for the stack cradle * It could be used to workaround for #195 (and other issues?) * And the api would be symmetric between both...
In https://github.com/haskell/lsp/pull/360, compatibility with `aeson >= 2` is achieved without using CPP, we want that too, because no one likes CPP!