Support Inspection of Immutable JS objects

[abritinthebay]

It's your own library guys - checking that it's Immutable and displaying the toJS output can't be that hard can it? ;)

But seriously - right now it doesn't even show the data when you expand it - just "fr" and an object with properties no-one care about.

Given that Immutable objects are becoming a recommended pattern (and FB has a library for it) this seems like a no brainer.

I'll see if I can fork + patch but would love to know if you're working on this...

[Daniel15]

+1 I'd love to see this too

[phuson]

+1

[wilkerlucio]

+1 I would love this feature as well

[zpao]

Going to merge this into #52.

[gaearon]

Immutable support is implemented in the latest version.

[lukeknep]

@gaearon Thanks for digging into this. Is the latest version released? I just updated to 2.1.7 (released today) and am still seeing Immutable Maps and Records visualized like arrays of size-2 arrays (rather than key / value pairs).

Ah, I discovered the explanation on #459 and it seems this behavior is expected.

As as devtools and Immutable user, it would be nicer/quicker to be able to see the key names for Maps, Records, etc. but sounds like that's a complex issue.

[gaearon]

I don’t think it’s too hard. Just needs someone dedicated to fixing it.

[vdh]

@gaearon So will Immutable.js Maps get a better implementation? Maps with string keys are really hard to read like this.