Tracking cabal executables

[lukexi]

I noticed that stack-ide doesn't seem to track files in executable targets (i.e. when I run stack ide myproject it only compiles/reports errors for the "library" section of the cabal file). Is there a way to do this?

(including test-suites would be great too)

[mgsloan]

I believe this has the same root cause as commercialhaskell/stack#347

While this isn't mentioned there, one thing to try might be to add an other-modules list for the executable. Not sure if that'll fix it, but cabal does support this field for executables / test-suites, though it doesn't demand it.

[drwebb]

I have the same issue when writing tests (really sucks for TDD). I'm on emacs and stack-mode properly load my tests module either when I run stack-load-buffer.

Since commercialhaskell/stack#753 I've been able to run stack ghci <packagename>:exec:<executable compenent>. Could the new way stack ghci finds dependencies be added some way to stack-ide?

[bixuanzju]

For the moment, I am adding an other-modules list for the executable to workaround this, works for me.

[chrisdone]

I added support for this in stack ghci. I'll add it to stack-ide soon.

[rvion]

as usual, big thanks !

[carymrobbins]

So does stack-ide only support library components currently?

[chrisdone]

No, it just needs a way in its UI to disambiguate Main modules between components.

[chrisdone]

#63

[chrisdone]

Closing as dupe of #63 which describes the point accurately.