Skip to content

Latest commit

 

History

History
96 lines (55 loc) · 3.75 KB

File metadata and controls

96 lines (55 loc) · 3.75 KB

juniper_graphql_ws changelog

All user visible changes to juniper_graphql_ws crate will be documented in this file. This project uses Semantic Versioning 2.0.0.

master

BC Breaks

  • Schema::Context now requires Clone bound for ability to have a "fresh" context value each time a new GraphQL operation is started in a WebSocket connection. (#1369)

    COMPATIBILITY: Previously, it was Arced inside, sharing the same context value across all GraphQL operations of a WebSocket connection. To preserve the previous behavior, the Schema::Context type should be either wrapped into Arc or made Arc-based internally.

  • Replaced ConnectionConfig::keep_alive_interval option with ConnectionConfig::keep_alive one as KeepAliveConfig. (#1367)
  • Made WebSocket connection closed once ConnectionConfig::keep_alive::timeout is reached in graphql-transport-ws GraphQL over WebSocket Protocol. (#1367)

    COMPATIBILITY: Previously, a WebSocket connection was kept alive, even when clients do not respond to server's Pong messages at all. To preserve the previous behavior, the ConnectionConfig::keep_alive::timeout should be set to Duration:::ZERO.

Added

  • ConnectionConfig::panic_handler field and ConnectionConfig::with_panic_handler() method allowing to specify PanicHandler for panics happened during execution of GraphQL operations. (#1371)

Changed

  • Merged graphql_transport_ws::NextPayload and graphql_ws::DataPayload into a single struct. (#1371)

Fixed

  • Inability to re-subscribe with the same operation id after subscription was completed by server. (#1368)

0.5.0 · 2025-09-08

BC Breaks

0.4.0 · 2024-03-20

BC Breaks

Added

Changed

  • Made fields of ConnectionConfig public. (#1191)

Previous releases

See old CHANGELOG.