Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vector fields are overwritten instead of merged #435

Open
dhruvkb opened this issue Apr 14, 2023 · 2 comments
Open

Vector fields are overwritten instead of merged #435

dhruvkb opened this issue Apr 14, 2023 · 2 comments

Comments

@dhruvkb
Copy link

dhruvkb commented Apr 14, 2023

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].

@matthiasbeyer
Copy link
Collaborator

Hi,

thanks for your report. I don't think lists should be merged necessarily, but I see that in some instances, users might want to merge lists.

@matthiasbeyer matthiasbeyer changed the title Vector fields are overwritten instead of merge Vector fields are overwritten instead of merged Apr 14, 2023
@dhruvkb
Copy link
Author

dhruvkb commented Apr 14, 2023

If not the predominant default behaviour, at least an option or workaround to merge lists would be great to have. Thanks for considering this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants