stack haddock ignores the dependencies of test suites and executables · commercialhaskell/stack#2620

(4 comments) (2 reactions) (0 assignees)Haskell (4,060 stars) (848 forks)batch import

component: haddockhelp wantedtype: enhancement

説明

General summary/comments (optional)

stack haddock generates the documentation for the dependencies of the library component, but not of the executable or test components.

Steps to reproduce

Create a cabal package where some packages are required by the executable or test but not the library
Run stack haddock

Expected

If I go to the doc index (.stack-work/install/x86_64-linux/lts-7.0/8.0.1/doc/all/index.html), I expect to see the executables and test suite dependencies docs.

Actual

They're not there.

Stack version

$ stack --version
Version 1.2.1, Git revision f28002bdea51468566fd9370f7f9e801c2b51bc5 (4141 commits) x86_64 hpack-0.14.1

Method of installation

Built from git.

コントリビューターガイド

技術スタック: なし
領域: clibuild systemdocumentation
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: Haskell build system knowledgeStack internalsCabal file structure
初心者向け度: 35
調査方針: Investigate how `stack haddock` collects dependencies for library vs test and executable components. Look at the stack code for the haddock command, likely in `src/Stack/Build/Haddock.hs` or similar. Examine how the dependency graph is constructed to ensure all component dependencies are included. Consider checking if there is an existing PR or discussion about this behavior.