digital-asset / digital-asset/dpm
componentsV2 version has incorrect value when the component is `local-file-path`
Open
Nobody has claimed this yet.
cleanup
- Dominant language
- Go
- Stars
- 3
- Forks
- 2
- Avg merge
- 21h 16m
- Merged PRs (30d)
- 1
Description
Local components don't have versions, but dpm resolve seems to populate the version field (under componentV2) containing arbitrary values (parent directory of the component or such) for them.
One would expect to have null or some known placeholder for the version
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 reproducing the issue with dpm resolve using the local component fixture in pkg/testutil/testdata/daml-package/unix/daml.yaml. Trace where the componentV2 version is populated for local-file-path; done means its version is null or a documented placeholder rather than an arbitrary path-derived value, with coverage for the fixture case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100