Instead of tweenState(function(state) {return state.a.b;}, config), maybe it's nicer to have tweenState(['a', 'b'], config) instead.
Pros: more idiomatic to immutable-js/mori. Shorter and probably slightly more intuitive. getTweeningValue looks much nicer.
Cons: not google closure advanced compilation mode compatible. Less type-checkable? Does anyone care?
Will leave this here and consider it. Don't wanna randomly break the API.
Instead of
tweenState(function(state) {return state.a.b;}, config)
, maybe it's nicer to havetweenState(['a', 'b'], config)
instead.Pros: more idiomatic to immutable-js/mori. Shorter and probably slightly more intuitive.
getTweeningValue
looks much nicer. Cons: not google closure advanced compilation mode compatible. Less type-checkable? Does anyone care?Will leave this here and consider it. Don't wanna randomly break the API.