fendor

Hello! Happy to hear it! True, I think so as well, these are the only locations where we access the Keys. To be frank, I am not fully sure right...

I am not working on it right now.

Stack doesn't allow an absolute path dir for the builddir, only relative to the work dir and claims it is Cabal's fault.

Hi! Is Lib2 listed as a module target? (Not sure about hie-bios but HLS definitely does not just find Modules in the include directories.) What does the output of `hie-bios...

Just checking, your build process, e.g. `bazel build` works as expected? I checked with just base flags, e.g. ```bash > ghc -package-id base-4.14.1.0 -package-id base-4.14.1.0 -optc-fno-stack-protector -ibackend/package-b/ -ibackend/package-a/ backend/package-b/src/Lib2.hs backend/package-a/src/Main.hs...

hie-bios is using `.hie-bios` script, but its session loading logic could be flawed... however, I assume HLS still doesn't work with that `.hie-bios` script?

I did not forget this issue, I can reproduce it locally, however, I currently don't know what causes the issue :(

That is indeed a good idea! I think the README is already a bit overloaded, do you think this information is so crucial it should be in the README or...

Yeah, the executable that comes with `hie-bios` which you can install via `cabal intall hie-bios` or `stack install hie-bios` offers an interface for debugging. ``` > hie-bios --help hie-bios version...

Would a format such as ```yaml cradle: cabal: dependencies: [] environment: - name: HOOGLE_DATABASE value: "~/.hoogle" ``` be helpful? Potential `CradleAction` type: ```haskell data CradleAction a = CradleAction { actionName...