Prettier + more-discoverable source for non-exposed modules

[tom-bop]

In the same way that I can currently click to see the source of any exposed module on hackage, it would be very nice to be able to see the test suite for a package.

(Maybe this is a larger issue? It would be nice to be able to see the source of e.g. executables and internal modules also. The test suite is definitely the most pressing to me, though.)

[gbaz]

You can click the [browse] link in the "download" section to look inside a package. We could try to make this more discoverable -- not sure exactly how, but perhaps related to #721

[tom-bop]

😮 I've been missing this, apparently, for many years. Discoverability would help, as would syntax highlighting (of the .{hs,lhs} files), and ideally links to definitions like the source files for exposed modules have.

[gbaz]

Where would the links to definitions go from?

[tom-bop]

I'm not sure I understand; what I'd imagine is something similar to what we have for exposed modules:

Currently, if I'm looking at the definition of lookupGT in an exposed module and I click "Key" in the type signature it takes me to the definition of Key.

Similarly, if I'm browsing the source and I click fromAscList, I'd imagine it would either take me to the corresponding source file or (less likely) to the exposed-module definition.

I'm unfamiliar with how haddock creates the current linked and syntax-highlighted docs, so I don't have an idea of how large or small the work for this enhancement would be.

[gbaz]

Oh, I see! The highlighting and hyperlinking of source is done by haddock. So this is sort of a docbuilder issue. There's options in cabal haddock for --executables --tests --benchmarks and --all but I haven't explored how they'd work with our existing docbuilder.