Opam Files: Better Locations
Open
Nobody has claimed this yet.
package management
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
At the moment, error messages when converting opam files to our lock directory leave much to be desired. The best we can do is point to the opam file that caused the error. It would be better if we could get the error to the concrete object (section, variable, filter, etc) that is causing the problem.
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 Dune's opam-file conversion and error-reporting entry points, then inspect how locations are retained for sections, variables, and filters. Done means conversion errors identify the concrete object causing the problem rather than only the source opam file; add or update coverage for those diagnostics where existing tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100