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
From what I find the time zone is unconditionally appended to the Datetime string before parsing with Moment. This yields all Datetime parseFormats that lack the trailing 'Z' ineffective. Including 5 from the default list.
From what I find the time zone is unconditionally appended to the Datetime string before parsing with Moment. This yields all Datetime parseFormats that lack the trailing 'Z' ineffective. Including 5 from the default list.
Behavior
In Model:
Setting "2019-11-22 17:30" through Admin UI should be valid.
Currently that's invalid, while setting
parseFormat: ['YYYY-MM-DD hh:mm Z']
makes the string "2019-11-22 17:30" valid in Admin UI.Environment
The text was updated successfully, but these errors were encountered: