Fix schedule view input #1021
Fix schedule view input #1021
Conversation
…iever component, action, and re
…ng service time range.
There was a problem hiding this comment.
I really like this change. I think it's a little confusing from a user perspective. See comment about the timezone alert bug.
If a user enters an invalid date, they should be made aware the request was invalid and the schedule did not update. Or the schedule should disappear, so users do not mistakenly assume the schedule represents the invalid date.
| const timezoneCode = formatTz( | ||
| isShowingSchedule && date | ||
| ? parse(date, inputDateFormat, new Date()) | ||
| : new Date(), // TODO: mock for percy tests, | ||
| 'z', | ||
| { |
There was a problem hiding this comment.
This is causing the timezone code to change & update in the alert if the year starts with 0, which is a little jarring as you're typing.
There was a problem hiding this comment.
Good catch! Fixed in 4d1e615.
Good catch, fixed in cc7e503. |
Description
This PR ensures that web requests to get stop times are made only when the user enters a valid date
within the service range available in OTP. Stop times requests when the date is invalid or out of range are no longer made.
Bonus UI: the browser will show the valid dates and sometimes prevent users from entering a date outside the range.
PR Checklist: