fix: use extend
with deep copy where necessary
#106
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we removed
extend
as a dependency, I didn't think the lack of deep copy would be an issue. That turned out to be incorrect as it caused issues concerning query parameters (and may have allowed issues in other areas as well). The "version" parameter would be overwritten by any query parameters from the generated code.I added
extend
back and reinstated every instance that we were using deep copy before. For instances that deep copy was not previously used, I left the code asObject.assign
.