feat: refactor to use Guzzle

[owenvoke]

Obviously this doesn't have to be used, but I thought I'd create a quick example of what this package could look like using Guzzle. 👍🏻

And here's a test script you can use:

<?php

declare(strict_types=1);

use RetroAchievements\Api\RetroAchievements;

require __DIR__ . '/vendor/autoload.php';

$username = getenv('RA_API_USERNAME');
$token = getenv('RA_API_TOKEN');

$client = new RetroAchievements($username, $token);

dump($client->getGameInfo(23796));

I'd also be happy to implement PHPStan and Pint for static analysis and code style formatting (or some tests). 👍🏻

[owenvoke]

All exceptions implement this, which allows for catching any RA client exception. 👍🏻

[owenvoke]

Not sure if these should be split into action traits based on the subtypes in the API docs. It would increase readability and discovery.

For example, getTopTenUsers() could be under a ManagesFeeds trait, and getGameInfo() and getGameInfoExtended() could be under ManagesGames 🙂

[owenvoke]

I've changed this to /API/ rather than lowercase, as otherwise it hits a 404 for all the requests. 🤷🏻

It's kind of a shame, but I assume this will be resolved when migrating to proper Laravel routes and controllers for the API. 👍🏻 Speaking of, are there any plans / a roadmap for this (I'd be interested in helping)?

[owenvoke]

Another possibility would be to create classes representing each resource, and then we would be able to map the values into these.

This would be similar to how the JS package uses it's model interfaces.

[wescopeland]

Hi @owenvoke!

I believe @luchaos may be otherwise engaged at the moment.

My perception is all of our API packages are intended to be reference wrappers around RAWeb's endpoints, similar to api-js. I'm sure you've already looked through api-js's source code, but if not it can be found here: https://github.com/RetroAchievements/api-js

[owenvoke]

Hi @wescopeland, thanks for the details. I modelled this off of the API (and looked into the JS package previously). The changes in this PR should cover the expectations. 👍🏻

I've got no issues with waiting for feedback, I was more adding that comment as a note for myself. 👍🏻