[Feature] Supporting Data-Dumps

[kaiserkiwi]

Hi there,

I recently found out that the IGDB supports Data-Dumps for Partners. As I became a partner recently this would be highly interesting for me.

Would it be complicated to integrate it into the package? I can work without it, but then I have to different implementations of connecting to the IGDB-API. So I thought it wouldn't hurt to ask for this feature. :)

[marcreichel]

@kaiserkiwi First of all, congrats on becoming a IGDB partner!

But, as I am not a IGDB partner myself, I'm afraid it might be quiet difficult (for me) to implement this feature, as I cannot test things etc.

But you might give it a try and implement it into this package if you want. I would happily review (and potentially merge) your pull request 👍🏼

[kaiserkiwi]

Thank you 😊

I was afraid that this will be the answer :D But I totally get it. I'll probably look into it, when I have time to implement it for me.

Just for documentation purposes for me in the future (or someone that wants to implement it):
The endpoints are pretty straight forward. There is a /dumps endpoint, that lists all the other endpoints and then endpoints for every model like /dumps/companies.
In there is a property with s3_url with the URL to download the full CSV and some other properties like file_name, size_bytes and the updated_at. Also there's a schema object with all properties that will be returned (like id: LONG and name: STRING).

The CSV is just a huge file with one entry per row, as you would expect it. The schema seems to be the base data of the entity without the eager loading of the relationships.

---

So I guess the main work would be to get the CSV files. How to work with these files probably shouldn't be part of the package. Or at least be the second iteration of this.