Releases: obmarg/graphql-ws-client
Releases · obmarg/graphql-ws-client
v0.10.1
v0.10.0
Breaking Changes
- All Connection trait functions now return impl Future instead of BoxFuture
(#108) - Removed the legacy API that was deprecated in v0.8.0
(#81) - The deprecated
async-tungstenite
feature has been removed. Use the
tungstenite
feature instead, which works withasync-tungtenite
,
tokio-tungstenite
and any other library that provides a
futures::{Stream, Sink}
based tungsetenite interface.
(#106)
Changes
- MSRV is now 1.76
- Updated dependencies (#100)
tungstenite
0.23
graphql_client
0.14
- Removed unused dependencies (#105)
async-trait
pin-project-lite
Contributors
Thanks to the people who contributed to this release:
v0.9.0
Breaking Changes
- The
no-logging
feature has been removed in favour of a defaultlogging
feature (#97)
New Features
- Added keep-alive functionality. When enabled this will send periodic pings
when the connection appears inactive. If these pings are not replied to, the
connection will be considered broken.
(#93, #94, #103) - Client is now Debug (#101)
Changes
- simplify keep alive implementation
- pin release-plz version (#91)
Contributors
Thanks to the people who contributed to this release:
v0.8.2
v0.8.1
Fixes
- Hopefully fixed the docs.rs build
v0.8.0
Breaking Changes
async_tungstenite
is no longer a default feautre, you should explicitly
enable it if you need it.- Updated to
tungstenite
0.21 - MSRV is now 1.69 (there was no official MSRV before)
- Subscription IDs sent to the server are now just monotonic numbers rather
than uuids.
Deprecations
These will be removed in a future version, probably in v0.9.0
AsyncWebsocketClient
and all its supporting traits and structs are now
deprecated.- The
async-tungstenite
feature flag is deprecated and will be removed in
favour oftungstenite
eventually.
New Features
- Added an entirely new client API as a replacement for the old API.
- Added a
subscribe
function tonext::ClientBuilder
to make
creating a single subscription on a given connection easier.
Changes
graphql-ws-client
now depends only ontungstenite
and not directly on
async-tungstenite
(ortokio-tungstenite
). This should allow it to work
with more versions of the async libraries (provided they support the same
tungstenite
version).
v0.8.0-rc.2
Breaking Changes
async-tungstenite
is no longer automatically enabled when adding any of the
client feature flags.
Changes
graphql-ws-client
now depends only ontungstenite
and not directly on
async-tungstenite
(ortokio-tungstenite
) This should allow it to work
with more versions of the async libraries (provided they support the same
tungstenite
version).
Bug Fixes
- Fixed
tokio-tungstenite
support by switching theasync_tungstenite
Connection
impl to a generic impl on anytungstenite
compatibleStream
&Sink
.
v0.8.0-rc.1
Breaking Changes
- The
next
api is now available at the top level rather than thenext
module. async_tungstenite
is no longer a default feautre, you should explicitly
enable it if you need it- Updated to
async_tungstenite
0.25 - Renamed
Client::streaming_operation
to subscribe innext
api. - MSRV is now 1.69 (there was no official MSRV before)
Deprecations
These will be removed in a future version, probably in v0.9.0
AsyncWebsocketClient
and all its supporting traits and structs are now
deprecated.
New Features
- Added a
subscribe
function tonext::ClientBuilder
to make
creating a single subscription on a given connection easier.
v0.8.0-alpha.2
Breaking Changes
Error::Close
now has a code as well as a reason.
New Features
- Added a
next
module with a significant re-work of the API
v0.8.0-alpha.1
This is the first in a series of alphas for v0.8.0, most of which will have breaking changes.
Feel free to test with this version, but you probably want to hold off upgrading till I'm closer to done.
Breaking Changes
- Subscription IDs sent to the server are now just monotonic numbers rather
than uuids. SubscriptionStream
no longer takesGraphqlClient
as a generic parameter- Removed the
GraphqlClient
trait and all its uses - Changed the
StreamingOperation
trait:- Removed the
GenericResponse
associated type decode_response
now always takes aserde_json::value
- I expect most
implementations of this will now just be a call toserde_json::from_value
- Removed the