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

fix: use extend with deep copy where necessary #106

Merged
merged 1 commit into from
Aug 6, 2020

Conversation

dpopp07
Copy link
Member

@dpopp07 dpopp07 commented Aug 6, 2020

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 as Object.assign.

Copy link
Member

@apaparazzi0329 apaparazzi0329 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

we recently removed extend as a dependency but this caused a bug - the lack of deep copy in Object.assign causes issues putting together query params
@dpopp07 dpopp07 merged commit 566b81f into master Aug 6, 2020
@dpopp07 dpopp07 deleted the dp/add-extend-back-in branch August 6, 2020 18:44
ibm-devx-automation pushed a commit that referenced this pull request Aug 6, 2020
## [2.4.4](v2.4.3...v2.4.4) (2020-08-06)

### Bug Fixes

* use `extend` with deep copy where necessary ([#106](#106)) ([566b81f](566b81f))
@ibm-devx-automation
Copy link

🎉 This PR is included in version 2.4.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link
Member

@mediumTaj mediumTaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 looks good!

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

Successfully merging this pull request may close these issues.

4 participants