Releases: kamranayub/GiantBomb-CSharp
Releases · kamranayub/GiantBomb-CSharp
v3.0.0 - RestSharp 107 upgrade
2.6.0: Use System.Text.Json deserializer
v2.5.0 - .net 5.0
Changes
Thanks to @chyyran
- Update to .NET 5.0
- Switch CI platform to GitHub Actions
- Update tests
- Update all dependencies (
RestSharp.Portable
->RestSharp
stable)
v2.4.0 - .NET Standard 1.2
- Switch to .NET Standard 1.2. Adds support for:
- .NET Core 1.0+
- .NET 4.5.1+
- Mono 4.6+
- Xamarin.iOS 10.0+
- Xamarin.Android 7.0+
- UWP 10.0+
- Windows 8.1
- Windows Phone 8.1
- Switch to Fubar.RestSharp.Portable
- More descriptive error handling
- Temporary: Remove
Game.ProductCodeType
because API returns incorrect response
v2.3.0
- BUG: Fixed deserialization exception for single resource errors (e.g. Object Not Found)
- BUG: Fixed synchronous API to not deadlock
- Removed fastJSON DLL since it wasn't actually being used
- Upgrade to RestSharp 105.2.3
- Added .NET 4.6 and 4.6.1 support
v2.2.0
- Upgrade to .NET 4.5.2 (you should too!)
- Upgrade RestSharp to 105.1
async/await
support for all methods- Better fatal error handling
- If GiantBomb returns a non-JSON response, the library will throw a
GiantBombHttpException
containing the raw response body
- If GiantBomb returns a non-JSON response, the library will throw a
- FIX: Issue with searches returning duplicate games from GiantBomb
v2.1.0
- Add new fields:
Platform.Aliases
Platform.InstallBase
Platform.OnlineOnly
Platform.OriginalPrice
Game.Franchises
Release.Game
- Add exception handling and wrapping for GiantBomb API errors (
GiantBombApiException
class)- For example, exceeding the 400 requests in 15 minutes rate limit
- Allow overriding
Execute
methods - Update RestSharp to 105 (fixes #13)
v2.0.3
2.0.3
- Fixes issue with search paging (
offset
vs.page
parameter)