Releases: dcastro/JSendWebApi
Releases · dcastro/JSendWebApi
v0.8.3
JSend.Client:
- Bug fix:
DefaultJSendParser
and NakedContentParser
now correctly handle empty responses.
v0.8.2
JSend.Client:
- Modified parsers to correctly handle responses with the 204 No Content status code
- Modified
JSendResponse<T>.EnsureSuccessStatus
to build a more log-worthy error message.
- Renamed properties
HttpRequestMessage
/HttpResponseMessage
to HttpRequest
/HttpResponse
for brevity
v0.8.0
JSend.Client:
- Added
NakedContentParser
, capable of parsing content not wrapped in a JSend "envelope"
- Added
JSendSchemas
- loads JSON schemas to validate a JSend message
- Moved parsers into the
Parsers
namespace
- Removed non-generic
JSendResponse
- Split
JSendResponse<T>
into 3 different types: JSuccessResponse<T>
, JSuccessWithDataResponse<T>
and JErrorResponse
v0.7.0
JSend.WebApi:
- Improved testability of JSendApiController
- Result types can now be instantiated (but not executed) even if the controller does not have a
HttpRequestMessage
or a UrlHelper
.
v0.6.0
JSend.WebApi:
- Added
IJSendResult<out T>
interface to enable composing used-defined results with out-of-the-box results.
v0.5.0
JSend.Client:
- Added support for .NET 4.0
- Added support for Windows 8
- Added support for Windows Phone 8.1
- Added support for Windows Phone 8 (Silverlight)
- Added support for Silverlight 5
v0.4.0
JSend.Client:
JSendClientSettings.SerializerSettings
are now used to deserialize HTTP response messages.
IJSendParser.ParseAsync
now takes a JsonSerializerSettings
as a parameter
v0.3.0
JSend.Client:
- Added support for relative URLs
- Added
CompositeInterceptor
- Added
HttpClient
and SerializerSettings
properties to IJSendClient
- Renamed
JSendResponseException
to JSendRequestException
- Wrapped
HttpRequestException
s with JSendRequestException
s