commercialhaskell/stack

stack haddock ignores the dependencies of test suites and executables

Open

#2,620 创建于 2016年9月22日

在 GitHub 查看
 (4 评论) (2 反应) (0 负责人)Haskell (4,060 star) (848 fork)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

  1. Create a cabal package where some packages are required by the executable or test but not the library
  2. 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
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Haskell build system knowledgeStack internalsCabal file structure
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
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.