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

Sets/Maps/WeakSets/WeakMaps (collections) are not reactive. #6774

Closed
prenaudat opened this issue Oct 11, 2017 · 2 comments
Closed

Sets/Maps/WeakSets/WeakMaps (collections) are not reactive. #6774

prenaudat opened this issue Oct 11, 2017 · 2 comments

Comments

@prenaudat
Copy link

Version

2.4.4

Reproduction link

https://jsfiddle.net/z93jk3py/

Steps to reproduce

Create computed value based on Set/Map/WeakSet/WeakMap. update collection, computed value not updated

What is expected?

Expect View to be updated on collection update

What is actually happening?

View not updated.


If not mistaken, development has been done to wrap Arrays methods (pop, push..). Should same be done for methods of aforementioned collections?

@posva
Copy link
Member

posva commented Oct 11, 2017

Most of those collections not being supported by all browsers we cannot support them yet. I thought this was discussed in another issue but I couldn't find it.
In any case, this is something that will be added to v3 when we drop support for older browsers (#5893 (comment))

@posva
Copy link
Member

posva commented Oct 11, 2017

Ah, found it: #1319 (comment) (thanks to #5241 (comment))
Just to be clear, it's something that we plan to add on a future version 🙂

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

No branches or pull requests

2 participants