Skip to content

Conversation

@gatl
Copy link

@gatl gatl commented Jan 26, 2019

While web_orders_gogdata() is able to acquire the most recent operations
in a user's history, occasionally we wish to go through its entirety.
This can be used to calculate the full amount already spent, determine
when a game was purchased or do more elaborate analysis such as how a
user changes behaviour or preferences since they created their GOG
account.

The new method was added with what are considered reasonable default
arguments.
At the same time, a new URL was added, supporting all the search
arguments for this query.

While web_orders_gogdata() is able to acquire the most recent operations
in a user's history, occasionally we wish to go through its entirety.
This can be used to calculate the full amount already spent, determine
when a game was purchased or do more elaborate analysis such as how a
user changes behaviour or preferences since they created their GOG
account.

The new method was added with what are considered reasonable default
arguments.
At the same time, a new URL was added, supporting all the search
arguments for this query.
@Yepoleb
Copy link
Owner

Yepoleb commented Jan 28, 2019

Thanks for your submission, but I've already decided to remove the web functions in the next push because they're all just really shitty and unmaintained. If you want to maintain a fork I'd link to it though, just tell me if you're interested.

@gatl
Copy link
Author

gatl commented Jan 28, 2019

As long as I can to do this, I don't really care what API is used. I will keep an eye on your future releases.

@greggameplayer
Copy link

@gatl thanks 🙂, i was struggling to find the needed params for the request to return values

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants