[NcDateTimePicker@v9.0.0-alpha.8] Errors and broken Polls app

[dartcafe]

I don't know where to start ...

1. ... to describe what happens
2. ... to describe what is needed to get things working again
3. ... to solve the problems in an appropriate time

First of all I get the following error
Uncaught (in promise) RangeError: Use dd instead of DD (in MM/DD/YYYY) for formatting days of the month to the input Fri Apr 04 2025 20:15:00 GMT+0200 (Mitteleuropäische Sommerzeit); see: https://github.com/date-fns/date-fns/blob/master/docs/unicodeTokens.md (vue-datepicker.js:4530:38)

This causes

• a broken sidebar
• impossibility to select dates for a poll
• a very very frustrated maintainer.

Of course you may try to fix the issues in Polls, but it will not work without changing concepts and a re-implementation from scratch.

I want to repeat my request to re-enable the prior NcDateTimePicker as a deprecated component (i.e. as NcDateTimePickerDeprecated), to get the chance to migrate the app to the new picker.

A preparation for the lib update can be found here

[ShGKme]

Thanks for the issue. We'll have a look with @susnux.

But if you have any specific examples, especially with Poll-specific use-cases - this would help a lot.

[susnux]

First of all I get the following error

Yes this comes from the switch to something standard instead of proprietary definitions.
The format string follows the Unicode tokens

Maybe we should simply add a good default formatting. Currently (and also in the v8 version) the default is either ISO formatting or US formatting. From the code of the polls app it seems you just want localized formatting, which makes sense.

[dartcafe]

Thanks for the issue. We'll have a look with @susnux.

But if you have any specific examples, especially with Poll-specific use-cases - this would help a lot.

Since I am not really able to see what is broken (it completely stopped working after the switch), it is rather complicated to describe the use case.

Polls allows to add multiple options for a date poll.
An option is a representation of a localized time and a duration (but stored as unix timestamp and duration in seconds).

• a whole day (timestamp: 2025-04-05 00:00:00, duration 0 or 24h)
• a moment of a day (timestamp: 2025-04-05 14:00:00, duration 0)
  Result: 2025-04-05
• a timespan within a day (timestamp: 2025-04-05 14:00:00, duration 1h)
  Result: 2025-04-05 14:00:00 - 2025-04-05 15:00:00
• a timespan of multiple days (timestamp: 2025-04-05 14:00:00, duration 48h)
  Result: 2025-04-05 - 2025-04-06
• a timespan across dates (timestamp: 2025-04-05 23:00:00, duration: 8h)
  Result: 2025-04-05 23:00:00 - 2025-04-06 07:00:00

The idea of the picker (and actual working functionality with Polls 7) is:

• open the picker
• select any day, time or range combination you want to add
• keep the picker open while selecting multiple options
• change to every allowed option combination (day, daytime with or without a range)

Example screen flow, what works now (Polls 7) :

step	presentation
Add new options by button click
Picker opens
Select a single day the selection is displayed as preview
Add the selection The picker stays open
Select a time
Go back to date
Change the date
Add the date time combination
Change to a range
Select a range with date and time
Add the range to the options

And so on and on and on

And now a BIG BUT, before the new picker gets more complicated as necessary because out of the use cases of a single app:

This functionality will be replaced by a modal, which is already available as a beta function in the current alphas and surely better compatible to the new picker. You can see it here: nextcloud/polls#3906 (comment)

This is the reason, why I would prefer just to have the old picker back as a deprecated component. This would give me time to make sure the new way will work as expected and I can introduce the new option modal as default without pressure.

[dartcafe]

Nevermind. I am migrating to the native picker instead of the old one and replace the old range picker.

BTW: @ShGKme Is it by intention, that the NcDateTimePickerNative uses the browser's locale instead the one the user has configured or is it a technical dependency?

[ShGKme]

BTW: @ShGKme Is it by intention, that the NcDateTimePickerNative uses the browser's locale instead the one the user has configured or is it a technical dependency?

Do you mean datetime-local? If yes - it's in the native picker, it's defined by the browser, and it uses the system locale.

[dartcafe]

Do you mean datetime-local?

Yes, right.

If yes - it's in the native picker, it's defined by the browser, and it uses the system locale.

Thought so.