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
This bug affects all previous versions of combine-json.
If a folder has the following structure:
/parent child.json // { "x": "X", "y": "Y" } /child/a.json /child/b.json /child/c.json
Depending on which one gets processed first, the result may be partial. For example if the order is this:
/child/a.json child.json /child/b.json /child/c.json
Then whatever is set in a.json is ignored. This is due to how lodash.set() works:
a.json
lodash.set()
const o = {} _.set(o, ['a', 'b', 'c'], { foo_c: 'bar_c' }) // { a: { b: { c: { foo_c: "bar_c" } } } } _.set(o, ['a', 'b'], { foo_b: 'bar_b' }) // { a: { b: foo_b: "bar_b" } } } } // notice that foo_c disappeared!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This bug affects all previous versions of combine-json.
If a folder has the following structure:
Depending on which one gets processed first, the result may be partial. For example if the order is this:
Then whatever is set in
a.json
is ignored. This is due to howlodash.set()
works:The text was updated successfully, but these errors were encountered: