haskell-nix/hnix

Replace every use of ErrorCall with a custom Exception value

Open

#309 opened on May 9, 2018

View on GitHub
 (5 comments) (3 reactions) (0 assignees)Nix (116 forks)github user discovery
good first issue

Repository metrics

Stars
 (835 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Rather than pass strings with rendered components to ErrorCall, every possible error or piece of information raised within hnix should use a specific constructor, retaining as much information as possible about the context of that information.

Contributor guide

Research direction
Examine all uses of `ErrorCall` in the codebase, categorize the contexts, and design custom exception types that retain context information.
Tech stack
haskell
Domain
backendcli
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
HaskellException handling in Haskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60