better locations in diff errors
Open
Nobody has claimed this yet.
cram
enhancement
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
When we get a differing cram test, the location we attach to the error should be the line where the first output changed.
This could probably be implemented in general for a diff action.
This would allow editors to jump directly to the differing output in the cram test.
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 tracing how differing cram-test output is reported and how the diff action assigns error locations; the issue does not name files or tests. Done means the location points to the first changed output line and editors can jump directly to that line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100