brandonchinn178 / brandonchinn178/toml-reader
Explicitly test parser + normalizer
Open
- Dominant language
- Haskell
- Stars
- 16
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
We use `toml-test` as a catch-all integration test, but we should probably include some explicit tests for various things.
We should also include tests that parser + normalization errors are the errors we expect
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing toml-test integration and the parser and normalizer entry points. Identify representative parser and normalization failures with expected errors, then add explicit tests whose passing results demonstrate the requested coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100