Timezone Option

[philliskiragu]

I am currently upgrading an old legacy project that is still using "eonasdan/bootstrap-datetimepicker" on bootstrap 3 and one of the most useful features we use from the package is the Timezone option. The option enables the project to maintain a specific timezone we define as opposed to the browser timezone. The use case is that a client who travels a lot will still be able to view dates in their "home" timezone regardless of their current location or support staff can view dates based on the client's location and not their own.

This option seems to be missing in Tempus Dominus v6. Does anyone has a solution for this?

@Eonasdan Is it a feature that was removed by design and if so is there a way to re-add it for this specific use case? I saw your announcement about halting new features and it is totally understandable. I am open to discuss sponsorship for it if it is something that can be done. Could you kindly direct me to the best channel to have that discussion?

[Eonasdan]

I looked at handling TZ a couple of times, but I never got a solution I was happy with. I borrowed code from day.js from some of the date parsing, but the TZ stuff didn't work quite right. There's code in the datetime.ts file with some attempts.

What is your use case, that is, what is your input/output format that you're expecting to use?

[philliskiragu]

Thank you for your reply.

In the older library, we pass the timezone as an option as follows:

$('#datetimepicker_datetime').datetimepicker({
      format:  date_format,  e.g. "DD-MM-YYYY HH:mm"
      timeZone: user_tz       e.g.  "America/Los_Angeles" 
    });

And on the browser the date picker will display according the user_tz

[Eonasdan]

I don't remember what v3 did with that lol. Are you looking for something like: "my business is in PDT, so the current time is 7am, but my user is in EST, so the time is 10am. I want the picker to display 7am, not the user's current time"?

[philliskiragu]

Yes that is what we are looking for.

[philliskiragu]

@Eonasdan do you think that is achievable?