1
98%
master: 98%

Ran 27 Sep 2016 09:36PM UTC

Files 14

Run time 2s

Badge

Embed ▾

Committed 27 Sep 2016 09:33PM UTC coverage: 97.536% (-0.7%) from 98.243%

Job # 318.1

Build Type

Pull #223

travis-ci

Committed by

web-flow

Commit Message

Refactor getter caching based on keypath state

The current version of NuclearJS uses a cache key consisting of store
states (monotomically incresing ID per store).  This has the
disadvantage of allowing only a single level of depth when figuring out
if a cache entry is stale.  This leads to poor performance when the
shape of a Reactor's state is more deep than wide, ie a store having
multiple responsibilities for state tracking.

The implementation is as follows:

- Consumer can set the maxCacheDepth when instantiating a reactor
- Getters are broken down into the canonical set of keypaths based on
the maxCacheDepth
- Add a keypath tracker abstraction to maintain the state value of all
tracked keypaths
- After any state change (`Reactor.__notify`) dirty keypaths are
resolved and then based on which keypaths have changed any dependent
observers are called

Pull Request Pull Request #223: Refactor getter caching based on keypath state

Run Details

752 of 771 relevant lines covered (97.54%)

89.65 hits per line

optimizely / nuclear-js / 318 / 1
98%
master: 98%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 318.1

optimizely / nuclear-js / 318 / 1 98% master: 98%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 318.1

optimizely / nuclear-js / 318 / 1
98%
master: 98%

README BADGES
x