recursive entry grouping for huge collections

[alexkuz]

(there's a lot of changes, I'm sorry for that, it probably shouldn't be in one PR)

• If Object, Array or Iterable has more than collectionLimit entries (50 by default), only collectionLimit entries are shown, the rest are grouped recursively (so than not more than collectionLimit groups are shown). If collectionLimit = 0, all items are shown.

Example screencast (as a part of redux-devtools-inspector):

• Added prop postprocessValue(value) (identity by default): allows to replace value on rendering. Useful for huge collections, as there is no need to traverse all entries, just the ones that are rendered.
• Added prop isCustomNode(value) (returns false by default): if returns true, item is rendered via JSONValueNode, which allows to render custom component for any type of item (not just literals). Should be used with valueRenderer.
• Objects with circular references are never expanded by default, even with expandAll = true.
• Some refactoring :)

[alexkuz]

btw, I'm not good at naming things, so if it's confusing, I would be glad to hear your suggestions :)
@gaearon

[alexkuz]

@chibicode please take a look!
I should warn though, it will break other PRs, because of refactoring.
But I really need it for https://github.com/alexkuz/redux-devtools-inspector :)

[chibicode]

@alexkuz I will asap, sorry I've been gone in Lake Tahoe last week

[gaearon]

From a very cursory glance this looks 👍 to me.

[chibicode]

Merged! @alexkuz I didn't get to read getCollectionEntries carefully, but I added you as a collaborator just in case you wanted to make further changes. (Also, thanks @gaearon for reviewing, I added you as a collaborator too, if you don't mind)

[chibicode]

@alexkuz published 0.6.0. I'll try to merge other PRs and publish 0.6.1 but not sure when I'll get to that

[chibicode]

@alexkuz trying to figure out how to incorporate this PR after the refactoring - could you help me out? https://github.com/chibicode/react-json-tree/pull/36/files

[alexkuz]

Thanks!
I'm not sure if that PR is still relevant - @leonaves, would you take a look? (if it is, would be helpful to see an example)

[leonaves]

From what I've seen it's not an issue that's affecting react-devtools-inspector anymore, but I'm not sure if that's because of these changes or what you've changed in rdi (i.e. it may be an issue that could still affect someone using react-json-tree). I'll take a look tonight and get back asap.