Closed pixelzoom closed 5 years ago
Answered my own question.
// @private {Array.<AnimationTarget>} - All of the different values that will be animated by this animation.
// If config.targets was supplied, those targets will be wrapped into AnimationTargets
// If config.targets was not supplied, the config from this object will be wrapped into one AnimationTarget
this.targets = _.map( config.targets === null ? [ config ] : config.targets, function( config ) {
return new AnimationTarget( config ); // TODO #3: strip out the irrelevant config when using config arg
} );
So I guess that all AnimationTarget
config
fields are fair game to put directly into Animation
config
. Seems like a big price to pay for that convenience.
Animation
uses theconfig
pattern, and it's documentation says:After having to look through the entire source code for
config
fields (which is what I really despise about theconfig
pattern in general), I can find no reference toconfig.to
anywhere inAnimation
.@jonathanolson can you please point me to where
config.to
is documented inAnimation
?