LazyValues are now cached on the scope object. This allows us to re-use streams as needed. For any given template, we are creating a datatree that the renderer can depend on to provide updated values when LazyValue.value is accessed. There is a single root node for each data item accessed and other helpers, subexprs and concats branch off from there. This means that LazyValues should not be destroyed until the scope is.
Tests have been added for the Rebound Compiler and the client side compiler is now able to accept component strings.
Test files are now in ES6.
Sauce Labs and Testem have been added to automatically test PhantomJS, N-1 for Evergreen Browsers and IE9+. All tests are passing!
LazyValues are now cached on the scope object. This allows us to re-use streams as needed. For any given template, we are creating a datatree that the renderer can depend on to provide updated values when LazyValue.value is accessed. There is a single root node for each data item accessed and other helpers, subexprs and concats branch off from there. This means that LazyValues should not be destroyed until the scope is.
Tests have been added for the Rebound Compiler and the client side compiler is now able to accept component strings.
Test files are now in ES6.
Sauce Labs and Testem have been added to automatically test PhantomJS, N-1 for Evergreen Browsers and IE9+. All tests are passing!