Skip to content

Graphql subscriptions can not be unsubscribed without triggering another one in the graphiql interface. #1125

Closed
@ygbourhis

Description

@ygbourhis

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

  • What is the current behavior?
    The current behaviour is that when you trigger a subscription in the graphiql interface, there is no way to stop the subscription without triggering a new subscription.

  • What is the expected behavior?
    The expected behaviour is shown bellow:
    https://youtu.be/2Aks6wnYeRc
    When a subscription is triggered, the "play" button should change into a "stop" button.

  • What is the motivation / use case for changing the behavior?
    Allow stopping subscriptions in the graphiql interface without necessarily triggering a new one.

  • Please tell us about your environment:

    • Version: graphene-django==2.15.0
    • Platform: Linux (python 3.6)
  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow)

Here is a Pull request which fixes the issue:
https://github.com/graphql-python/graphene-django/pull/1124/files

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions