Bump 1.3.0

Changed

• Redis subscriptions store configuration has been decoupled from AnyCable, so you can use any broadcasting adapter and configure Redis as you like. [@palkan] (#44)

1.1.7: Depend on anycable-core gem

Changed

• Depend on anycable-core gem instead of anycable.

  This allows to avoid installing grpc gem when using alternate AnyCable broadcasting adapters (like HTTP).

  See #43 for details.

1.2.0: Stats, anycable-core dependency, dropping legacy

Added

• Stats collection about subscriptions, channels, etc via GraphQL::AnyCable.stats. [@prog-supdex] (#37)

  See Stats section in README for details.

• Configuration option redis_prefix for namespacing Redis keys. [@prog-supdex] (#36)

Changed

• Depend on anycable-core gem instead of anycable.

  This allows to avoid installing grpc gem when using alternate AnyCable broadcasting adapters (like HTTP).

  See #43 for details.

Removed

• Handling of client-provided channel identifiers. BREAKING CHANGE

  Please make sure that you have changed your channel disconnected method to pass channel instance to GraphQL-AnyCable's delete_channel_subscriptions method.
  See release notes for version 1.1.0 for details.

• Handling of pre-1.0 subscriptions data.

  If you're still using version 0.5 or below, please upgrade to 1.0 or 1.1 first with handle_legacy_subscriptions setting enabled.
  See release notes for version 1.0.0 for details.

1.1.6: Redis.rb v5 compatibility

Fixed

• Fix empty operation name handling when using redis-client or redis.rb v5. [@ilyasgaraev] (#34)
• Fix deprecation warnings for redis.rb v4.8+ and support for redis.rb v5. [@smasry] (#29)

1.1.5: Fix deprecation warning for `use_client_provided_uniq_id` (again)

• Fix that deprecation warning about config.use_client_provided_uniq_id again, so it can be issued outside of Rails. [@gsamokovarov] (#27)

1.1.4: Fix deprecation warning for `use_client_provided_uniq_id`

• Fix deprecation warning about using client-side channel ids shown even if deprecated functionality was disabled in application code (not via config file or environment variable). [@gsamokovarov] (#26)

  However, now deprecation warning won't be shown if graphql-anycable is used not in Ruby on Rails application.

1.1.3: Allow using with GraphQL-Ruby 2.x

Changed

• Allow using graphql-anycable with GraphQL-Ruby 2.x (it seem to be already compatible). [@Envek]

1.1.2: AnyCable 1.3.0 and Redis.rb 5.0 support

Fixed

• AnyCable 1.3.0 compatibility. [@palkan] #21
• Redis.rb 5.0 compatibility. [@palkan] #21

1.1.1: Fix bugs on unsubscribe

Fixed

• Handling of buggy istate values on unsubscribe (when use_client_provided_uniq_id: false). [@palkan] #20
• A bug when #unsubscribe happens before #execute. [@palkan] #20

1.1.0: Allow not to rely on client-generated channel ids

Added

• Support for generating unique channel IDs server-side and storing them in the channel states.

  Currently, we rely on params["channelId"] to track subscriptions. This value is random when using graphql-ruby JS client, but is not guaranteed to be random in general.

  Now you can opt-in to use server-side IDs by specifying use_client_provided_uniq_id: false in YAML config or thru the GRAPHQL_ANYCABLE_USE_CLIENT_PROVIDED_UNIQ_ID=false env var.

  NOTE: Relying on client-side IDs is deprecated and will be removed in the future versions.

  You must also update your cleanup code in the Channel#unsubscribed:

-        channel_id = params.fetch("channelId")
-        MySchema.subscriptions.delete_channel_subscriptions(channel_id)
+        MySchema.subscriptions.delete_channel_subscriptions(self)