haskell / haskell/hackage-server
Show dependencies for library and executables separately
- Dominant language
- Haskell
- Stars
- 467
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
When I look at the package on Hackage and I want to compare this package with other packages, I evaluate number of dependencies of the library as a part of comparing process. Unfortunately, this is not an easy thing to do, because currently Hackage shows dependencies for both library and executable in the same section. Consider `life-sync` package:
* http://hackage.haskell.org/package/life-sync
Currently dependencies for this package look like this:
```haskell
Dependencies | ansi-terminal,
base-noprelude (>=4.9 && <5), bytestring, containers, exceptions, fmt, life-sync,
microlens-platform, optparse-applicative, path,
path-io, process, relude (>=0.1.0), text (>=1.2), tomland (==0.3.*)
```
So the `Dependencies` section contains dependencies for both library and executable. If I press the `details` button I can see separation between library and executable. But I'm looking at Hackage for 3 years and noticed the `details` only now. It would be really great if the separation between package components was clearer. For example something like this:
```haskell
Dependencies
library (62)
ansi-terminal, base-noprelude (>=4.9 && <5), bytestring, containers,
exceptions, fmt, microlens-platform, path, path-io, process,
relude (>=0.1.0), text (>=1.2), tomland (==0.3.*)
executable:life (64)
base-noprelude, containers, life-sync, optparse-applicative, path
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the Hackage package page's Dependencies section and its details view, then trace how component dependencies are rendered. Implement clearer separation for library and executable dependencies, and verify the package page displays each component and its dependency list distinctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100