matchLine tests and better documentation
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 19
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
maybe some assertions of properties that matchline outputs, and make it more obvious what matchLine output.
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 locating the matchLine implementation and checking its current output shape. Define assertions for the properties it returns and update the relevant documentation so the output is clear; done means the tests cover the agreed properties and the documentation explains matchLine output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100