Linters for libraries
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 1.6k
- Forks
- 210
- PR merge metrics
- No merged PRs in 30d
Description
HLint currently only ships with linters for libraries in the base package. I should expand that, and let anyone contribute additional ones. However, I'd need some kind of module scoping so that importers for unused libraries aren't applied all the time. e.g. if you import Data.Pretty then the pretty hints are used. There is one example is #12, but I can think of lots more.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing library linters shipped in HLint and the example referenced by issue #12. Determine how additional linters could be contributed and how imports such as Data.Pretty would scope their hints. Done means library linters are extensible and only activate for relevant module imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100