HAR: Dart trailing YAML comments end up in the parsed version
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 63/100
Research direction
Start at parsePubspecNameVersion in the Dart push path and compare its line based parsing with the pinned harness/harness-cli reference, push_npm.go. Check how the project manages Go dependencies before adding gopkg.in/yaml.v3. Done when trailing comments on name and version are excluded from parsed values; no test file is named in the issue.
Written by the indexing model from the issue text.
Description
Bucket: P (hc did this right before the port, ours differs)
Source issue: #4 from internal HAR porting triage
hc behaviour
Uses gopkg.in/yaml.v3 to parse pubspec.yaml (dependency present in hc since 2026-01-27).
Current gap
parsePubspecNameVersion in the Dart push path is line-based ("no YAML library dependency" per code comment), so trailing YAML comments on the version/name lines get captured as part of the value.
Fix approach
Add a YAML library dependency (gopkg.in/yaml.v3) and parse pubspec.yaml properly instead of line-matching.
hc reference
Match this against the original implementation in harness/harness-cli (hc), pinned at commit 0772e94: push_dart.go
- Dominant language
- Go
- Stars
- 25
- Forks
- 13
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from harness/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
beta
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
stage-fail
Difficulty 1/5 Under an hour Newbie friendliness 72/100
siyuan-note/bazaar#2405 ·
Maintainers usually reply within 1 day
-
bug priority: high workstream:cache
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rossoctl/context-guru#707 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prime-radiant-inc/evener#5028 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100