mlabs-haskell / mlabs-haskell/lambda-buffers
Sort out error/info/warning reporting
Open
Nobody has claimed this yet.
frontend
ux
- Dominant language
- Haskell
- Stars
- 32
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
As @jaredponn said in https://github.com/mlabs-haskell/lambda-buffers/pull/147#discussion_r1396843860 for more context see https://github.com/mlabs-haskell/lambda-buffers/issues/144
Contributor guide
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 issue #144 and the discussion in pull request #147, which provide the available context for error, info, and warning reporting. The issue does not identify files, tests, or a concrete completion condition, so the reporting behavior and scope need to be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100