Minor bug - seems weird to be able to schedule in the past

[nus-pe-bot]

Really just nitpicking here, but can consider maybe prevent scheduling in the past, cos it seems abit weird

---

_{[original: nus-cs2103-AY1920S1/pe-interim#688]}

[qiujiaaa]

Team's Response

Our team has considered that issue when designing our application, but we did not include such a constraint for our users because:

1. We took into consideration that our user might forget to input any impromptu schedules in our application before the actual meetup, the user will then not be able to add it into the system if we impose this constraint. Since the schedules are also included in our archives later on, user might not be able to know the exact time/date in future while browsing through the archived orders.

2. Orders in our system can only be completed if it is scheduled. If our user forgets to input the schedule in our application (and actual meetup already happened), they will then be forced to input a future schedule just to be able to complete the order. This might cause incorrect data records due to the wrong date/timing of the schedule for that order.

Hence, our application does not impose such a constraint on our user, idea is similar to how we can still add events to past dates on our phone calendars.

Duplicate status (if any):

--