fix and improve value rendering

[Domiii]

TODO

• [x] to better investigate the bug of constructValueObjectShallow and constructValueFull add a way to investigate their "raw data" in DebugTDNode
  • expose all relevant data and their connections, if possible
  • consider AsyncTDNode.makePromiseLinkTree: it also gathers all relevant data to visualize a complex (recursive and non-linear) hidden data structure
• [x] fix omitted value rendering

More Issues

• [x] Test + fix error handling: when an object's children's serialization errors out, is the error message is readable in the object's prop?
  • [x] find a way to easily reproduce, maybe:

    var o = eval(`({ x:1, get y() { throw new Error('Y FAILED'); } })`);
    console.log(o);

• [ ] future work: change how we iterate keys. It currently ignores class getters and more.

Examples

• see this options object from sequelize#5...
  • NOTE: I reloaded from file. Not sure, if its related to that, or just a bug in Value rendering?
• same thing happens with only parts of the document.location object in todomvc:

[MiccWan]

The valueRef of the child nodes are actually Omitted, which is not rendered correctly. I've fix the rendering of omitted values. But the reason they are omitted is still not found yet.

Note: There are some 'ReadError' while serializing TextDecoder.

[MiccWan]

Find out why, when the first time a read errors out, the error message is not readable in the object's prop (or is it and we have not seen it)?

When a ReadError occurs with an actual Error, the trace cannot be produced successfully. Thus we cannot inspect the error message. See getter-error.js.