You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Hello,
Is there a way to enforce which timezone should be used /considered when selecting / saving the date?
For example :
we organize an event in Moscow (UTC+3) but I am currently in London (UTC+1)
I want some action to be triggered at 3:00 in Moscow.
So 0:00 UTC should be saved in the database.
So I understand that by default, I should enter 1:00 on the ion-datetime-picker so that 0:00 is saved in the database because I am in London.
What I want is to be able to enter 3:00 on the ion-datetime-picker even though I am in London, because I know my event is in Moscow.
Is that possible ?
Thank you :)
Nicolas
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
Is there a way to enforce which timezone should be used /considered when selecting / saving the date?
For example :
we organize an event in Moscow (UTC+3) but I am currently in London (UTC+1)
I want some action to be triggered at 3:00 in Moscow.
So 0:00 UTC should be saved in the database.
So I understand that by default, I should enter 1:00 on the ion-datetime-picker so that 0:00 is saved in the database because I am in London.
What I want is to be able to enter 3:00 on the ion-datetime-picker even though I am in London, because I know my event is in Moscow.
Is that possible ?
Thank you :)
Nicolas
The text was updated successfully, but these errors were encountered: