covidshots.in helps you find, and book vaccination slots in India. You can set it to automatically book new slots, or just to monitor for new slots and sound alarm.
Running - A loading sign, a message saying "Looking for slots" or something to indicate that auto refresh is running in the background
Booked - We only see a notification on the top right which disappears. Can we also have a message saying "Slot booked for
Can we use the space on the yellow band on top to show such messages?
When we have multiple sessions for the same day for a centre our side doesn't handle it.
For example for the sample centre we can have following sessions at the same time
covishield 18-45
covishield 45+
covaxin 18-45
covaxin 45+
Our site was coded with the assumption of only a single session for a centre for a given day.
eg. Cowin shows 141+50 == 191 vaccines for day3 below.
Or site only shows 50 ie. data from one of the sessions, not a cumulative of both.
getjab, etc. In what way they are better, our strengths, what features we can borrow.
List existing solutions Indian users have access to.
List unique features of each
List things/ideas we should borrow
Performance testing - check if our site is faster when notifying a user about new slots or if other solutions are. I believe our site would be the fastest since the polling is done on every user's computer rather than on a central server. Hence delay between detecting new slots, and notifying all users is not there. The cowin API also places limits on the number of requests in a given period of time. Hence a central server is a bad idea.
Expected Result: The Auto book button has been clicked and there is some indication that auto book is running
Actual Result: The auto book button isn't clicked so the user has to click it again (and if the user is me, she assumed she has clicked it and moves on and expects it to work)
Because of this our code tries to find user details from g_persistent_vars.g_booking_state_users_details_get().
We are not clearing user details so im not sure why his would be an issue. would have to debug more.
The essence of the issue is that once a new mobile number is used it causes issues with older cached data.
We can fix this issue in one of the two ways.
Make details stored with mobile number, ie. objects referenced with mobile numbers
Clear mobile number specific info when a new mobile number is seen.
The districts should be fetched as soon as states drop down is closed. The vaccine centres should be fetched as soon as the districts drop down is closed.
This will improve UI and will get rid of the following bug.
Bug ; Select delhi in states, click get districts. Go back to states drop down and remove delhi and select goa. Dont click get districts in this case. Just go to districts drop down. You will see that it lists districts from delhi even though the states dropdown only has goa and doesn't have delhi.
$.fn.dataTable.ext.type.order in index.js
handles sorting.
Now with new ui (issues #22, and #14) the data structures have changed.
So this no longer works, and has been commented out.