* fix-dynamic-to-with-array-values:
WIP sync github pages
chore: update examples list
chore: re-order list of examples
fix: the video example wasn't working sometimes
breaking: add a dynamic option controls whether objects and arrays passed to `Tween.to()` can be dynamically modified during animation.
unit tests and examples for #555
Improved yoyo documentation
It wasn't clear from the documentation that I had to pass anything into the `yoyo` function. I had to go look at the yoyo example page to figure that out. Hopefully this change will make it clear to the next person.
The yoyo function currently has no code block example. This leaves it up to the user to guess whether calling the function sets yoyo to true or if a value needs to be passed in without referring to the code. Added lines to show that boolean values should be passed in to the function.
Adds a new `dynamic` option to the `to()` method. If set to true, objects are passed in an used directly by Tween. This allows outside code to modify values dynamically during animation (including interpolated array values). Tween will modify the initial interpolation arrays. If `dynamic` is set to false, the object passed in will be copied and will never be modified, but in this case it is not possible to modify the object values dynamically during animation.
The breaking change is that, when dynamic is false, Tween makes a non-inheriting hard copy of the object passed into `to()` instead of making an prototypal "copy" that inherits values from the original object.
The reason for this breaking change is that now things are consistent: when `dynamic` is set to `false` (the default) no object passed into `Tween.to()` will ever be modified AND those objects can never be used for dynamic updates (whereas before, objects could be dynamic, but arrays were not). Likewise, when `dynamic` is `true`, then both objects and arrays can be modified on the outside and Tween will animate based on those changes.
* master: (38 commits)
update dist files
rename some tests to better reflect what they test
improve the conditional logic more so that values in nested arrays can also be animated
add and example and test for animating values in an array
start values aren't arrays, only to values are
move _updateProperties function back out to a method
fix yoyo with array values test
temporary, move updateProperties function to make diff with master more clear
move some code and update variable names to make mergin with master easier (less conflict)
update dist
improve state reset when stopping and starting a tween (fixes#512 where yoyo wouldn't restart properly)
move value-swapping code for repeated tweens to a function (it will be re-used in an upcoming change)
consolidate duplicate handling of relative values
update dist files
ignore VS Code's config folder
small refactor to prevent update from doing anything when a tween has finished, yet still allow tweens to go back in time
fix lint error
rename _isFinished to _isComplete to match other wording
add one more test for relative array values
add editorconfig to settings editors can be consistently unique (because we use tabs so people can set their own tab width)
...
