Including this in the field template for editing end_time
had the effect of forcing the end date to be set to the
current time instead of the current value of that field,
which is unusual behavior. It also caused the form to
have an automatically-invalid input state when editing
a reservation with a start time that falls in the future.
Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
<ng-template #endTimeTemplate let-field="field" let-record="record">
<eg-datetime-select
domId="endTime"
- ngModel
[showTZ]="editDialog.timezone"
[timezone]="editDialog.timezone"
[egNotBeforeMoment]="momentizeIsoString(record['start_time'](), editDialog.timezone)"