Skip to content

Releases: jegfish/goroyale

GoRoyale v0.4.0

19 Jul 23:52
Compare
Choose a tag to compare

Breaking Changes

  • Removed Client.PlayerVerification endpoint as it is going to be removed from the API.
    screenshot from 2018-07-19 19-47-24

Bug Fixes

  • Removed unused imports in errors.go

GoRoyale v0.3.3

17 Jul 04:57
Compare
Choose a tag to compare

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

12 Jul 18:07
Compare
Choose a tag to compare

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

01 Jul 21:32
Compare
Choose a tag to compare

New

Client.PlayerVerification endpoint method

GoRoyale v0.3.0

18 Jun 19:58
Compare
Choose a tag to compare

Quick breaking change. Removed Get from the front of all endpoint methods, as it was unnecessary.

GoRoyale v0.2.0

18 Jun 19:26
Compare
Choose a tag to compare

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 struct
  • Client.GetPrepTournaments endpoint method, PrepTournament struct

Breaking

  • Removed Args, ClanSearchArgs, and TournamentSearchArgs
  • Endpoint methods now take url.Values (just map[string][]string) for parameters to pass in the query string to the API. Used for:
  • Changed field names in OpenTournament (therefore also KnownTournament), PopularTournament, and TournamentSearchEntry.
  • Many of the structs I just mentioned have had their names changed
    • TournamentSearchEntry => SearchedTournament
    • OpenTournament/KnownTournament => Tournament
  • New RatelimitError and APIError structs to allow error handling.