fendor

> And what about change cabal-helper to configure/build the project with --test --bench --no-run-tests --no-run-benchmarks I like that idea, to make it at least configurable.

@tuomohopia > `ChLibName ChMainLibName with source directory: [\"src\",\"src/schema\",\"src/api\",\"src/Questions\",\"src/Users\"]` this is your library component. Can you share the resulting .cabal file? I *thought* that multiple source directories are invalid, so maybe...

@0xd34df00d We are currently not supporting diagnostics for `Setup.hs`. E.g. we can not load this into the IDE. @kirillFedorov1 Unless you have the same issue as @0xd34df00d, you should not...

@0xd34df00d Maybe you have opened it by accident before that? Requests to compile files are queued and executed in order. I can not imagine any other reason why else hie...

Then please post the logs for it. Alternatively, you can also try to invoke `hie --debug app/Main.hs` and see if this reproduces the error.

@kirillFedorov1 You have to specify a `none` - cradle. Given this `hie.yaml` ```yaml cradle: cabal: - path: "./test/dispatcher/" component: "test:dispatcher-test" - path: "./test/functional/" component: "test:func-test" - path: "./test/unit/" component: "test:unit-test"...

Can you provide all logs please? For vscode, https://github.com/alanz/vscode-hie-server#investigating-and-reporting-problems

Then you have to change the component syntax and the tool at the top to `stack`. For stack components, see the command `stack ide targets`

No need to apologize :) I think it looks already almost correct, Ill take a stab in the dark and suggest it should look like this: ```yaml cradle: multi: #...

The `hie.yaml` is correct, hie trips over some windows issue. @jneira I think you have encountered this issue before?