feat: add setOptions and setAxis method

[malangfox]

Details

Among the cases of using Axes, there is a case of directly changing the options of an Axes instance such like below.

...
    const axes = this._axes!;
    const axis = axes.axis[AXES.POSITION_KEY];
    axis.circular = [controlParams.circular, controlParams.circular];
    axis.range = [controlParams.range.min, controlParams.range.max];
    axis.bounce = parseBounce(flicking.bounce, camera.size);
...

This add setOptions and setAxis methods to change the options related to the Axes instance to simplify use cases like this.

Changing Options

AxesOption

Changing easing, interruptable can be applied to an animation currently in progress.
Changing maximumDuration, minimumDuration, deceleration applies when calculating to play the animation on next time. If you want to change the remaining time of an animation that is playing too, you may use updateAnimation method.
Changing round, nested can applied after inputs that made after changing these options.

AxisOption

Changing range, bounce, circular can applied after inputs that made after changing these options.
If the current position is outside the range set in the new option, it does not move the coordinates within the range directly since it can trigger change event.
However, when next user input occur, new range will be applied in the process of calculating the new position. Triggering change event to position within range.

[daybrush]

LGTM

[WoodNeck]

I think this will remain in the build, please check whether it does.
As Object.assign isn't supported in IE

• https://developer.mozilla.org/ko/docs/Web/JavaScript/Reference/Global_Objects/Object/assign

[WoodNeck]

Also, aren't there any internal updates required for this change?
Check this example of updating options in View360

• https://github.com/naver/egjs-view360/blob/52b16b26a3b6397fef6e7798bfc9874e1a4166a3/src/YawPitchControl/YawPitchControl.ts#L390

Like, nested may require some immediate update of event handlers.

[malangfox]

It looks like this changes should avoid using Object.assign for browser compatibility. Confirmed that it remains after the build.
Also changing the nested option will not require any changes to the event handler.
We are using the following statement to add property to native event.

    if (!this.options.nested || !this._isEndofAxis(offset, depaPos, destPos)) {
      nativeEvent.__childrenAxesAlreadyChanged = true;
    }

Since the option is checked when each change is made, the changed option will be applied from the next input without changing any event handlers.

[malangfox]

If there are parts that need immediate change, it may be current animation being played that duration needs to be changed by minimum/maximum duration option.
Also it will be necessary to discuss about action when the current range is outside of the new range.

[WoodNeck]

Same here, you can do it rather like this, and the typescript compiler(+ bundler) will do the work

this._axis[key] = {
  ...this._axis[key],
  ...axis[key]
}

[WoodNeck]

LGTM