Version v3.2.0

Minor release adding some features. Most notably the transition for new API for ignorable fields. Currently all properties under the statics property name is ignored, but this is a poor and weak API. We’ll transition to a more explicit API through decorator helpers. This release is obviously non-breaking, so the statics property behaviour isn’t removed yet, but will be with the next major release.

Added “hot swapping” of functions passed in statics. This is to swap out event handlers passed with a cursor reference. See #68

As Omniscient encourages more work in the render function, you might have to do additional work even though some of your data is unchanged. We added omniscient.cached to allow for cached functions, dependent on input. Example:

Version v2.0.1

Fixes:
1. Tests and examples use Immutable.js 3.0.0 and Immstruct 1.0.0.
2. Fixed bug with shouldComponentUpdate and children (#19).

Version v2.0.0

As of v2.0.0, Omniscient is dependent of React v0.12.0. This React version introduces some changes, and no longer allows components, but elements. With this some changes, not too big but breaks the previous API.

Statics as properties

The most notable change is that the statics are moved to be a part of the properties.
Statics still doesn’t effect whether or not the component should update.

Before you could do:

OmniscientComponent('someKey', cursor, statics);

But now you have to do:

OmniscientComponent('someKey', { cursor: cursor, statics: statics });

As a result of this, you now always get passed props to your render function.