ndmitchell / ndmitchell/hlint

Define custom HLint rules

Open
#335 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
1.6k
Forks
210
PR merge metrics
No merged PRs in 30d

Description

e.g. groupBy ((==)onfst) $ sortBy (compareonfst) should be replaced with groupSortOn. Perhaps have an "hlint" test that only runs if hlint is on the PATH, so I have it fixed locally, but the buildbots don't need to compile hlint?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating how HLint defines and tests custom rules, then inspect how the groupBy/sortBy example could be represented as a suggestion. Check how an optional hlint test could be run only when hlint is on PATH without requiring buildbots to compile it. Done means the proposed rule and optional test approach are defined and covered by the relevant test setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.