We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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].
nums
[3, 4]
[1, 2, 3, 4]
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
If not the predominant default behaviour, at least an option or workaround to merge lists would be great to have. Thanks for considering this.
No branches or pull requests
Consider the following config.
This is built and given two config files.
The output of this configuration is that
nums
has only[3, 4]
. Vectors should be merged, andnums
should contain[1, 2, 3, 4]
.The text was updated successfully, but these errors were encountered: