You say it’s ‘such a common use case’, can you provide some examples of all the places that would need it? I’m just curious because personally I don’t want to see this new API being bloated with redundant fields (which I believe was something Helix was trying to avoid), when from my experience it would only be a very small set of developers that would need to have the game title and avatar included in every single streams request result.
An additional API request is quite insignificant when you consider that a games name will be infrequently changing and so is something that can easily be cached and stored so that to translate a game ID into a name can be done on your side, and not through Twitch. Same for an avatar too. And even if for whatever reason you don’t store a map of game ID’s to game names, you still don’t need the game name returned every single request to the stream because if the game ID didn’t change from the last time you polled the stream, the game name didn’t change either so you would only need to make additional requests to the games api when the game ID changes.