Describe the bug
Currently, DUP are bookable if a user is on the site at 6:59 and when it rolls over to 7:00am the greyed out box becomes clickable. To prevent any possibility of skipping the line, and improve user experience, we need to force users to refresh if they are on the site before 7:00am, or bookable only after arriving after 7:00am.
When it rolls over to 7:00am, proceed with booking a pass, without needing a refresh
Expected behavior
Users should be required to refresh prior to booking passes at 7am.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Developer approach could be to pull system time from the /api/config endpoint, and use that as the current tme instead of new Date() in the front-end in order to show/hide certain options in the UI. Calculating calculating based on the user's tz or currently set time(and sometimes incorrect) puts the browser into modes that are not reflective of actual server-based timings.
Prior to the user hitting next after selecting facility/date/type and immediately going to the turnstile, we may want an additional check on whether that is an allowable action before the front-end goes through the turnstile challenge.
Describe the bug Currently, DUP are bookable if a user is on the site at 6:59 and when it rolls over to 7:00am the greyed out box becomes clickable. To prevent any possibility of skipping the line, and improve user experience, we need to force users to refresh if they are on the site before 7:00am, or bookable only after arriving after 7:00am.
To Reproduce Steps to reproduce the behavior:
Expected behavior Users should be required to refresh prior to booking passes at 7am.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
/api/config
endpoint, and use that as the current tme instead ofnew Date()
in the front-end in order to show/hide certain options in the UI. Calculating calculating based on the user's tz or currently set time(and sometimes incorrect) puts the browser into modes that are not reflective of actual server-based timings.