Releases: jegfish/goroyale
Releases · jegfish/goroyale
GoRoyale v0.4.0
GoRoyale v0.3.3
Minor breaking change to how rate limits are handled. goroyale.RatelimitError
no longer exists. Your method calls will wait until a request is ready instead of returning an error when dealing with rate limits.
GoRoyale v0.3.2
This version doesn't contain any breaking changes.
Rate limit handling was updated to work with the newly changed headers in RoyaleAPI.
GoRoyale v0.3.1
New
Client.PlayerVerification
endpoint method
GoRoyale v0.3.0
Quick breaking change. Removed Get
from the front of all endpoint methods, as it was unnecessary.
GoRoyale v0.2.0
There were changes in the RoyaleAPI's tournament endpoints and in how endpoint methods take special arguments/parameters.
Changes
New
Client.Get1kTournaments
endpoint method,Tournament1k
structClient.GetPrepTournaments
endpoint method,PrepTournament
struct
Breaking
- Removed Args, ClanSearchArgs, and TournamentSearchArgs
- Endpoint methods now take
url.Values
(justmap[string][]string
) for parameters to pass in the query string to the API. Used for: - Changed field names in
OpenTournament
(therefore alsoKnownTournament
),PopularTournament
, andTournamentSearchEntry
. - Many of the structs I just mentioned have had their names changed
TournamentSearchEntry
=>SearchedTournament
OpenTournament
/KnownTournament
=>Tournament
- New
RatelimitError
andAPIError
structs to allow error handling.