Not understanding how updateOptions() works

[ericsua]

Hi,
I'm trying to implement two linked date time pickers (just two hours:minutes pickers) but I don't understand how the updateOptions() works.
If I execute updateOptions() two times on a single date time picker, do I keep the options I set before?
e.g.
linked1.updateOptions({ display: { viewMode: "clock"} })
linked1.updateOptions({ restrictions: { minDate: new Date() } })

I expect that after the second update the picker has the restriction AND the viewMode as clock, but it's not happening.
I read the docs and the source code and it seems that it should merge the new options with the previous ones, unless reset=true is provided.
Am I doing something wrong? Is this the default behaviour? If not, is there any way of updating the options keeping the ones that were set before?
(I'm using the latest dev version of Tempus Dominus)
Thanks

[Eonasdan]

updateOptions does work but viewMode doesn't. If you do something like this you will see that the options are merged.

 setTimeout(() => {
                datetimepicker1.updateOptions({ display: { viewMode: "clock"} })
                console.log('update clock')
                console.log(datetimepicker1.optionsStore.options)
            }, 1500)

The viewMode option not working on update is a bug which I'm now working on.

[ericsua]

Oh ok, thanks.
I tried also with the restrictions and maybe it's not working too.
I tried setting a minDate and a maxDate and the minDate was lost.
Example on StackBlitz here

const picker = new tempusDominus.TempusDominus(
  document.getElementById('datetimepicker1'),
  {
    restrictions: {
      minDate: new tempusDominus.DateTime().startOf('minutes'),
    },
  }
);

picker.updateOptions({
  restrictions: {
    maxDate: new tempusDominus.DateTime('2022', '5', '5'),
  },
});

[Eonasdan]

Hello. I'm coming back to this. The latest version seems to work correctly. If you still have an issue please let me know