Feature Request: Report reason for match failure
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
It would be very useful if rather than a simple true / false, there was some sort of info returned about why the code did not match the structure. This could be a helpful text string, or perhaps something more formal.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the JavaScript matcher that currently returns a boolean and reviewing its callers, then clarify the diagnostic format and expected failure cases. Done means the behavior is specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100