-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[BUGFIX canary] Create new hash when merging parameters hashes in components #12542
Conversation
AFAIK, this is still canary. |
Would love to see this merged and in canary.. |
👍 Confirmed that this fixes the issue in our app. Thanks, @Serabe ! |
@Serabe is correct, this feature is only in canary so no channel back porting needed. |
export function mergeHash(original, updates) { | ||
return assign(original, updates); | ||
export function mergeInNewHash(original, updates) { | ||
return assign(Object.create(original), updates); |
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.
Do we need object inheritance here? Would the following also work:
assign({}, original, updates);
…ponents When merging two parameters hashes coming from components/closure components we want them to be merged into a new hash. This refactors does not only make this happen but it changes `mergeHash` into `mergeInNewHah` to be explicit about this. Fix emberjs#12537
@rwjblue fixed. @stefanpenner comment was because I forgot to tag it, not because of canary/beta. |
Ahh, gotcha. Thanks for updating the prefix. |
Looks good to me, I restarted the sauce labs job. |
[BUGFIX canary] Create new hash when merging parameters hashes in components
Thanks for jumping on this so quickly @Serabe! |
When merging two parameters hashes coming from components/closure components we
want them to be merged into a new hash. This refactors does not only make this
happen but it changes
mergeHash
intomergeInNewHah
to be explicit aboutthis.
Fix #12537