v6.7.13 maxDate option crashes the plugin

[johncrislasta]

Prerequisites

• I have searched for duplicate or closed issues.
• I have validated my setup against the latest version on StackBlitz.
• I have read the contributing guidelines.

Describe the issue

I have installed v6.7.13 and I'm getting an error when I set the maxDate in the restrictions option.

The error is:

Uncaught TypeError: Cannot read properties of undefined (reading 'localization')
    at set viewDate [as viewDate]

I tested my setup on the stackblitz provided, but it worked:
I discovered that using a lower version, 6.7.7 worked.
I'll just use that version until the issue is fixed on the latest release.

Thanks!

StackBlitz fork

https://stackblitz.com/edit/tempus-dominus-v6-simple-setup-cwswbe?file=index.js

What operating system(s) are you seeing the problem on?

Windows

What browser(s) are you seeing the problem on?

Chrome

What version of are you using? You can find this information from the sample StackBlitz.

6.7.13

What your browser's locale? You can find this information from the sample StackBlitz.

en-US

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• tempus-dominus-v6-simple-setup (Open reproduction)
• tempus-dominus-v6-simple-setup-cwswbe (Open reproduction)

[Gandhi11]

Same things is happening with the minDate restriction.

[Gandhi11]

After digging a little bit it look like it is related to the changes done for #2828

[apircher]

I have the same problem. The error occurs in the viewDate setter when the viewDate is set from _initializeOptions - before this.optionsStore.options is assigned.

The setter tries to call this.optionsStore.viewDate.setLocalization(this.optionsStore.options.localization) but this.optionsStore.options is undefined.

It happens if there is a maxDate and the viewDate (i.e. new Date()) is after the maxDate or if there is a minDate and the viewDate is before the minDate.

[solomax]

Also reproducible for me ...
Everything works as expected with 6.7.11

[youlead-bow]

We also have the bug

[Eonasdan]

New release should fix this.