You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might look like an expandable list of times next to every pairing entry.
Conveniently, we are already storing everything needed to add this as a feature! Availabilities are currently stored as a JSON array of 1s and 0s for each hour of the week. For example...
means that whoever has availability avail is free from 6am-7am on Sunday, corresponding to avail[0][6], and 3am-4am on Monday, corresponding to avail[1][3] (early bird gets the worm).
So to implement this feature, you need to get the form_id of a given signup (it makes sense to only show this for the form actively being interviewed on, so check out services/form.ts:getActiveInterviewFormID), and then get the user's pairing for this form. Once you have both of the pair members' user_ids, find their signup for the form_id, which contains their availabilities.
The text was updated successfully, but these errors were encountered:
This might look like an expandable list of times next to every pairing entry.
Conveniently, we are already storing everything needed to add this as a feature! Availabilities are currently stored as a JSON array of 1s and 0s for each hour of the week. For example...
means that whoever has availability
avail
is free from 6am-7am on Sunday, corresponding toavail[0][6]
, and 3am-4am on Monday, corresponding toavail[1][3]
(early bird gets the worm).So to implement this feature, you need to get the
form_id
of a given signup (it makes sense to only show this for the form actively being interviewed on, so check outservices/form.ts:getActiveInterviewFormID
), and then get the user's pairing for this form. Once you have both of the pair members' user_ids, find their signup for theform_id
, which contains their availabilities.The text was updated successfully, but these errors were encountered: