-
Notifications
You must be signed in to change notification settings - Fork 4k
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
feat(codebuild): improve merging of BuildSpecs #15332
Conversation
@rix0rrr for visibility |
} | ||
|
||
function mergeDeep(lhs: any, rhs: any): any { | ||
lhs = JSON.parse(JSON.stringify(lhs)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer doing a fully recursive function here that type-analyzes, of the form:
function mergeDeep(lhs, rhs) {
if (Array.isArray(lhs) && Array.isArray(rhs)) {
return [...lhs, ...rhs];
}
if (Array.isArray(lhs) || Array.isArray(rhs)) { return rhs; }
if (isObject(lhs) && isObject(rhs)) {
const ret: any = {...lhs};
for (const k of Object.keys(rhs)) {
ret[k] = k in lhs ? mergeDeep(lhs[k], rhs[k]) : rhs[k];
}
return ret;
}
return rhs;
}
This will take care to create new objects instead of mutating when necessary, and otherwise structurally reuse when not.
If you MUST, I would accept a single parse(stringify(x))
on both structures at the start, to make sure nobody is holding "illegal" references to the starting structures that would be structure-shared in the final result. But we don't need to parse(stringify(x))
at every level of the recursion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sweet, thanks!
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
First steps for aws#15169 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
First steps for #15169
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license