dhall-lang/dhall-haskell

Low test coverage for dhall-to-{json,yaml,yaml-ng}

Open

#1,562 opened on Nov 19, 2019

View on GitHub
 (11 comments) (2 reactions) (0 assignees)Dhall (222 forks)batch import
help wantedjson/yaml

Repository metrics

Stars
 (968 stars)
PR merge metrics
 (Avg merge 3d 13h) (5 merged PRs in 30d)

Description

Bugs like #1559 and #1560 reveal that our current tests don't cover some very basic cases. Since conversion to JSON and YAML is such an important functionality, we should try to ensure that it works correctly.

Contributor guide

Research direction
Examine existing test suites for dhall to json, dhall to yaml, and dhall to yaml ng. Identify common edge cases (e.g., empty records, optional fields, union types) that are missing. Write Haskell test cases using the project's testing framework (e.g., tasty). Run tests and ensure they pass. Consider using QuickCheck for property based testing.
Tech stack
None
Domain
cli
Issue type
Test
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
Haskell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50