Skip to content

Conversation

HcySunYang
Copy link
Member

@HcySunYang HcySunYang commented Jan 14, 2021

Fix #3007

⚠️ NEEDS fix INSTEAD OF feat when squashing commit

@LinusBorg
Copy link
Member

LinusBorg commented Feb 1, 2021

I think we should consider this a fix:, not a feat:. I don't think we ever meant for collections to act as fully reactive when wrapped in a shallowReactive, so this implements the behavior that was originally intended.

Opinions?

If we agree on that, the commit message has to be changed to reflect properly in the CHANGELOG.

@HcySunYang
Copy link
Member Author

If we squash and merge, we can reset the commit message, right?

@LinusBorg
Copy link
Member

Think so, yes.

@LinusBorg LinusBorg changed the title feat(reactivity): support shallow readonly for collections fix(reactivity): support shallow readonly for collections Feb 3, 2021
@LinusBorg LinusBorg added 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: reactivity and removed 🔍 review needed labels Mar 12, 2021
@yyx990803 yyx990803 merged commit 68de9f4 into vuejs:master Mar 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. scope: reactivity

Projects

None yet

Development

Successfully merging this pull request may close these issues.

that shallowReadonly proxy of Map call get will return a proxy

4 participants