1 comment (1 comment)0 reactions (0 reactions)0 assignees (0 assignees)Haskell2,358 stars (2,358 stars)205 forks (205 forks)batch import
good first issuetesting
Description
They are messy at the moment.
Contributor guide
- Tech stack
- None
- Domain
- testing
- Issue type
- chore
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 2
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-3 hours
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- Basic HaskellLiquid Haskell basics
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 50
- Research direction
- The issue lacks specific details about what aspects of the test cases need cleanup. Start by examining the existing test files for liquid haskell in the repository to identify patterns of messiness. Check for any linked comments or maintainer guidance, and consider asking for clarification on what constitutes acceptable organization. Given the age of the issue, verify if the repository structure has changed.