Vector fields are overwritten instead of merged
Open
Nobody has claimed this yet.
C-enhancement
S-waiting-on-design
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
Consider the following config.
struct Conf {
nums: Vec<i32>
}
This is built and given two config files.
# a.yml
nums:
- 1
- 2
# b.yml
nums:
- 3
- 4
The output of this configuration is that nums has only [3, 4]. Vectors should be merged, and nums should contain [1, 2, 3, 4].
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
No source file, test, or entry point is named. Reproduce the Rust configuration example with a pair of YAML layers, then trace the layered merge path for Vec values. Done means values from both files are retained in order as [1, 2, 3, 4], with regression coverage added where the existing merge behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100