[MM-73]: Fixed the issue of getting invalid start/end time even though they were set

[Kshitij-Katiyar]

Summary

The start/end time was auto-selected when we opened the modal to create an event but still got the error that they were invalid. So fixed it by removing the autoselected value.

Ticket Link

Fixes #73

Ticket Link

1. Run /gcal event create
2. Update the subject and click on submit, the meeting should be created.

[mickmister]

Alternatively we could have the initial/default value be given by the parent component. If the UX flow for the empty value seems fine then we can keep that solution

Edit: I didn't mean to close the PR

[fmartingr]

Seems a good enough compromise. 👍

[mickmister]

@matthewbirtch When the "create event" modal is opened, what value should be shown in the "end time" date selector initially? Should be filled (e.g. with the current date), or be left blank?

[matthewbirtch]

@matthewbirtch When the "create event" modal is opened, what value should be shown in the "end time" date selector initially? Should be filled (e.g. with the current date), or be left blank?

@mickmister the default end time should be 30 minutes from the default start time.

[wiggin77]

@Kshitij-Katiyar @fmartingr customer is asking for an update on when this fix will be delivered. Please advise.

[Kshitij-Katiyar]

@Kshitij-Katiyar @fmartingr customer is asking for an update on when this fix will be delivered. Please advise.

@wiggin77 We are working on this. Only the QA review is left here.

[fmartingr]

@Kshitij-Katiyar @fmartingr customer is asking for an update on when this fix will be delivered. Please advise.

@wiggin77 We are working on this. Only the QA review is left here.

Can you provide an estimate on when QA is going to be completed/take place?

[AayushChaudhary0001]

This PR has been tested for the conditions stated in the description. The event got created easily and there were no issues in the setting the time for the event. This looks good to me, Approved.