Message from JavaScript discussions

August 2017

— I need to tune it more carefully since it is not full coverage yet

— 

Spec.js:112 Accessor "0" was visited 1 time(s).
Spec.js:112 Accessor "1" was visited 1 time(s).
Spec.js:112 Accessor "id" was visited 2 time(s).
Spec.js:112 Accessor "name" was visited 4 time(s).
Spec.js:112 Accessor "username" was visited 2 time(s).
Spec.js:112 Accessor "email" was visited 2 time(s).
Spec.js:112 Accessor "address" was visited 2 time(s).
Spec.js:112 Accessor "website" was visited 2 time(s).
Spec.js:112 Accessor "company" was visited 2 time(s).
Spec.js:112 Accessor "otherUser" was visited 2 time(s).
Spec.js:112 Accessor "street" was visited 2 time(s).
Spec.js:112 Accessor "suite" was visited 2 time(s).
Spec.js:112 Accessor "city" was visited 2 time(s).
Spec.js:112 Accessor "zipcode" was visited 2 time(s).
Spec.js:112 Accessor "geo" was visited 2 time(s).
Spec.js:112 Accessor "lat" was visited 2 time(s).
Spec.js:112 Accessor "lng" was visited 2 time(s).
Spec.js:112 Accessor "active" was visited 2 time(s).
Spec.js:112 Accessor "catchPhrase" was visited 2 time(s).
Spec.js:112 Accessor "bs" was visited 2 time(s).

— I also log stuff at the bottom

— Ahaaa

— For that graph 2 visits is normal for those accessors since there are two mirrored sections

— Kinda fun :P

— The problem with logging is the state for the IDDFS is very large and varies, depending on a single flyweight

Message permanent page

— So either you get too many logs to read them all, or your logs are not reflecting the real state at the time of the log

Message permanent page

— I just rely on breakpoints XD

— Hmmm, why not use Proxy?

— In what way?

— Just make some enumerable props, and have the Proxy tick them off when they get accessed