• 70 results
  • 1
  • 2
#51 Edited by soup_menu (228 posts) -

@frobie: Sounds good to me. Thanks for following up.

#52 Edited by soup_menu (228 posts) -

@frobie: At the risk of asking a stupid question: what is the function of the resource type ids? Right now they seem redundant. I can't find a scenario where you'd call /game with a type other than 3030 or where you'd use type 3030 with a resource other than /game. The apparent redundancy makes me think that (1) I'm missing something, (2) they're important internally, but those of us on the outside can just replace "/game/" with "/game/3030-", or (3) they're redundant right now, but in a future revision of the API they'll have an obvious use.

Would you mind setting me straight?

#53 Posted by frobie (111 posts) -

@soup_menu: It's just to make things easier internally for us.

#54 Edited by Vager (1654 posts) -

@frobie: I'm occasionally noticing a chat showing up on chats resource that's inaccessible by users. I assume it's you guys working on the chat privately. Any way we can get field to show this? Or just have this this type of chat hidden on the API. The last one of these happened late Friday night.

#55 Edited by frobie (111 posts) -

@vager: I'll fix it to return chats past the publish date instead of before the buffer time.

#56 Posted by Vager (1654 posts) -
#57 Posted by peteace (16 posts) -

It seems the number_of_total_results field is returning the wrong data now. Specifically, if I call http://www.giantbomb.com/api/games/?api_key=<KEY>&format=json&field_list=number_of_total_results, I would expect it to return the total number of games in the database, but it seems to be returning the number of results on the page, which I believe the number_of_page_results field is for. Let me know if I'm misunderstanding these fields, but it always used to return the total number of games in the database, at least until about a week ago it seems.

#58 Posted by frobie (111 posts) -
#59 Posted by peteace (16 posts) -
#60 Posted by LordAndrew (14430 posts) -

Something is wrong with sorting. I haven't checked everything, but from what I've checked:

  • http://www.giantbomb.com/api/games/?sort=date_added:desc shows the most recent additions as expected, but the results are sorted in ascending order within the response.
  • http://www.giantbomb.com/api/franchises/?sort=date_added:desc is sorting by date_last_updated.
  • http://www.giantbomb.com/api/franchises/?sort=date_last_updated:desc is sorting by date_added.
#61 Edited by frobie (111 posts) -

@lordandrew: Fixed and should be in production tomorrow. Tomorrow has arrived and the fixes are live.

#62 Posted by LordAndrew (14430 posts) -

@frobie: Franchises seem to be fixed.


But the others still give incorrect results.





#63 Posted by frobie (111 posts) -
#64 Posted by Avenged (28 posts) -

Is it possible to have a range for filter? Coud be nice for release dates.

#65 Edited by frobie (111 posts) -

@avenged: The date fields can now be filtered by a range of dates. The start and end date is separated by a pipe. Using one date will be considered as filtering for the exact date.


To get the locations that were added to Giant Bomb between 1/1/2012 and 3/1/2012:

http://api.giantbomb.com/locations/?api_key=[API KEY]&filter=date_added:2012-01-01%2000:00:00|2012-03-01%2000:00:00

To get the locations that were added Giant Bomb on 1/1/2012 (unfortunately needs an exact time stamp match):

http://api.giantbomb.com/locations/?api_key=[API KEY]&filter=date_added:2012-01-01%2019:45:08

#66 Edited by subkamran (20 posts) -

@frobie, is it by design to add a container around platforms in search results? Previously it was simply an array of platform objects, now it's an array of containers with a "platform" property that points to a platform. This is messing with my deserialization strategy :( I just noticed this recently. Was there a reason to change it? It's inconsistent now. The game detail resource still acts correctly, "platforms" is an array of platform objects.

Another question: how come all the images are crazy big? Small is still pretty big (601W) and Medium is huge (902W). Fun fact: if I change the URL for a Medium image to use "scale_tiny" it's a more palatable size (300x320). However, "tiny_url" returns a square cropped image, not "scale_tiny" as I'd expect. I'm using Last of Us as a reference.

#67 Posted by Avenged (28 posts) -

@frobie Any plans to add a DLC listing to game(s)?

#68 Edited by Ragowit (34 posts) -
#69 Posted by frobie (111 posts) -

@subkamran: I think I replied in another thread, but just to be sure, fixed the container issue in search results. Images (as well as videos) have been bumped up in terms of size relative to the old site.

@avenged: Possibly in the future as its own separate resource call.

@ragowit: We store the release dates as full dates regardless if its fuzzy or not. I'll have to investigate further, but we may store it as the first of the month or first of the year if its just a year so sorting by fuzzy release dates are off. I can provide the key we use to determine the date's fuzziness--so the sorting will be on the client end.

#70 Posted by Sly_Ripper (1 posts) -

Is there a way to use the filter to exclude? The way you've tagged games with platforms is silly, PSN games aren't tagged with the PS3 platform, yet a PS1 game that released on the store will have a PSN tag too.

Either that or allow us to filter search results, this was first requested 4 years ago.

#71 Posted by LordAndrew (14430 posts) -

The sort issue still exists for games, but the rest of the resources do seem to have been fixed. This isn't new, it's actually been this way since it was "fixed" two months ago, but I haven't had to the time to come back here and report it again.

  • http://www.giantbomb.com/api/games/?sort=date_added:desc&field_list=date_added
  • http://www.giantbomb.com/api/games/?sort=date_last_updated:desc&field_list=date_added,date_last_updated
  • http://www.giantbomb.com/api/games/?sort=name:asc&field_list=date_added,name