Hello,
I would like to give my opinions on a few functions i have checked.
Migration status document list community api “pet master list” function is being migrated to Game data api “pet index” function.
However, “pet index” seems to lack creatureId information along with lots of others. CreatureId is used as npc id to create wowhead tooltip or link to wowhead page.
Also, as you have mentioned under FAQ post, in many cases game data api requires multiple calls. But this is especially bad for game data index functions (that return a collection of items or realms or whatever) since they contain very little useful information, and you are almost always guaranteed to make lots of individual function calls to gather information for each entry.
For example, game data api “realm index” contains id, realm slug and realm name (in all localizations if no input locale parameter is set). Since there is no realm localization information in this function return, which localized name to use cannot be determined here. These information has to be gathered by making individual function calls for each realms to get realm information. Slug name returned by “realm index” has some unicode char differences from community api values. Also no connected realm information under “realm index” function, you need to make a call to “connected realms index”, which return a list of hrefs which you have to call each of them individually to get connected realms for each realm.
In this example, data that can be gathered with 2 function calls (community api “realm master list” and game data api “realm index” and joining them) now has to be gathered by making hundreds of function calls.
Again, for Item class and subclass list, data that can be gathered by making one call to get all class and subclass information from community api has to be converted to making an item class index call then individual calls for each class to get their subclass. This case is not as bad as realm information gathering case, only 20 calls instead of 1, but is a general trend for game data api’s index functions.
I hope you will have more time to review this migration process and consider making some adjustments or additions to current game data api functions, porting current community api functions to your new infrastructure. In its current state, this process looks more like a service shutdown of community api than migration to game data api.
Regards,