Hey, thanks for your feedback! In the following i’ll explain some points why i did certain things:
→ What’s start and end?
→ Each match “object” has start_time and end_time, with a human-readible date format (And then I found out you put it as UNIX timestamp, that’s great for computers)
Ok, i must admit i could have named these startTime and endTime. Since these are (currently) the same for all matches per region, it’s completely useless to add them for each match item – ~1000 bytes of useless overhead – also due to the suboptimal time format which you would parse to a timestamp or a better human readable format in most cases anyway.
→ Why EU and NA “objects” have indexed values (“1”: {}, “2”:{}, “3”:{}, …) instead of making them an array?
→ Each match object has it’s match id, composed by 2 numbers. I suppose the ones that start by 1 is one region and the ones that start by 2 is the other, and then they’re numbered. But you really can’t split this thing, as it’s an id. You really shouldn’t care about what does it mean
→ I wouldn’t split the id’s. I would do {"EU":{"1-1":{…},1-2,“NA”:{"2-1":{…},2-2. (or changing 1 by 2, idk which is eu and na…) Id’s can’t be splitted. They identify something. [Actually, the id’s should be “EU-1”..“EU-N” and “NA-1”…“NA-N” but… that could be hard to change]
The match_id isn’t actually an ID but 2 IDs, joined by a hyphen: the region and the matchup tier. I still wonder why Anet chose this format instead of having 2 parameters for the match_details.json like region and tier, both optional so that you could retrieve the match_details for all, a region or a single match if you like. That way it would make the life for database maintainers like millenium.org way easier since you wouldn’t need to loop through the matches.json and call the API 17 times to get the data for all matches.
As soon as i saved the gist yesterday, i realized that it would be much better to have the region IDs instead of “EU” and “NA” as identifiers. You may have noticed that it’s currently impossible to access the data for a single matchup or the start and end times for a specific region directly: you have to loop through the whole thing, and check for the match_id since the response is completely unordered. (i have already updated the gist added a regions object which holds the region IDs with the corresponding region to make it a little more descriptive)
So if you had a JSON like mine, you would just do this:
var matchData = {...} // the JSON response
var match = matchData.matches[2][3]; // data for match id 2-3 which is the EU tier 3 matchup
If you still need to loop through the whole thing (or lets say through all matches in a region) you could do this:
var regionID = 1; // your region id of choice, from a config or wherever you want
// prototype.js
// http://api.prototypejs.org/language/Hash/prototype/each/
$H(matchData.matches[regionID]).each(function(match){
console.log(regionID+'-'+match.key); // match id
console.log(match.value); // match worlds
//yada yada yada...
});
In PHP it could be something like this:
$json = '{...}'; // get it e.g. via file_get_contents()
// the second parameter for json_decode makes it an associative array
// i prefer these over objects because of the more handy syntax
$matchdata = json_decode($json, true);
$match = $matchdata['matches'][2][3]; // EU tier 3 matchup
$regionID = 1;
foreach($matchdata['matches'][$regionID] as $tier => $worlds){
echo $regionID.'-'.$tier;
print_r($worlds);
// ...
}
)
