Add support for unnamed collections.

[santiagopuentep]

A collection created for client-side only with new Collection(null) is not shown in the devtools. This would be very useful even if it's shown with a randomized name.

[leonardoventurini]

Interesting, I didn't know those were a thing... I will certainly research that!! Thank you again. 😃

[santiagopuentep]

Here's a thread about it.
link

[linegel]

@leonardoventurini hello, in our project we use heavily use local collections and it will be a big thing for us to have such kind of support. I could start the implementation of it, but it would be cool to have a few tips from you about where I can start implementing it

[leonardoventurini]

@leonardoventurini hello, in our project we use heavily use local collections and it will be a big thing for us to have such kind of support. I could start the implementation of it, but it would be cool to have a few tips from you about where I can start implementing it

It should be pretty easy to implement, I just didn't have time until now, but I plan on working on small patches for the extension this weekend and add support for it. something tells me it should be easy if possible at all.
sorry, I didn't have time to make the project more contribution-friendly I guess, but you certainly could take a look at the bridges, message handlers and the mobx stores! it all works around that. the extension cannot interact directly with the page's javascript so we need to use chrome's messaging api... etc.
it is all in typescript so the structure and intent of the code should be apparent-ish! 😄