Created
August 26, 2017 22:33
-
-
Save jeanpaulsio/e534814f568a0c9a2b743fce0f493077 to your computer and use it in GitHub Desktop.
Time Data Structure
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
0 - Sunday | |
1 - Monday | |
2 - Tuesday | |
3 - Wednesday | |
4 - Thursday | |
5 - Friday | |
6 - Saturday | |
*/ | |
data = | |
[ | |
{ | |
id: 2 | |
date_as_string: "Next Tuesday" | |
times: [ | |
{ | |
id: 1 | |
time_string: "8:00am" | |
}, | |
{ | |
id: 2 | |
time_string: "8:30am" | |
}, | |
] | |
}, | |
{ | |
id: 3 | |
date_as_string: "Next Wednesday" | |
times: [ | |
{ | |
id: 1 | |
time_string: "8:00am" | |
}, | |
{ | |
id: 2 | |
time_string: "8:30am" | |
}, | |
] | |
}, | |
] | |
Well, I matched yours exactly AND made one that I think is better...
https://github.com/Johnsalzarulo/uvohealth#available-times-endpoint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To put things in a little more perspective - i don't expect the data to come in already ordered:
I imagine it's probably more like this:
I still need a unique id for each of these values but I'm ok with ditching the "id" concept if we can guarantee that these times are spit out of the API in order