JuliaCI / JuliaCI/LocalCoverage.jl
robust path management and package specification
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 79
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Currently we map a package or a module to a path using undocumented internals (cf #30 which changes this).
I am not aware of a robust mechanism for doing this, other than calling internals. I wonder if we could just default to working on the current project.
It is still not clear how to query the path of the resulting cov files (again, other than hacks).
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
Start by reviewing issue #30 and the current package/module-to-path mapping. Clarify how the current project should be selected and how resulting coverage-file paths can be queried; done requires an agreed robust mechanism rather than undocumented internals or hacks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100