Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Regressions with "graphql-sse" subscription handling with altair-static. #2737

Open
1 task done
MurrayFurtado opened this issue Dec 10, 2024 · 1 comment
Open
1 task done

Comments

@MurrayFurtado
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I have migrated from v7.0.1 to v8.0.5 and observe the following problems:

I configure initialSubscriptionRequestHandlerId: "graphql-sse" in my RenderOptions object and pass this to the renderAltair() method, along with a query and a subscription endpoint. When I click on run subscription I notice that once the subscription returns, it continually re-executes the query until I press cancel and it appends the duplicate results in the results window.

Secondly when I open the Request Handlers dialog I expect my Subscription Handler value to be set to Graphql Over SSE but it's still set on "websocket".

All this functionality used to work in v7.0.1 (except I had to specify initialSubscriptionsProvider: "graphql-sse" instead of initialSubscriptionRequestHandlerId)

Expected Behavior

When I click on run subscription it should just run my subscription query once.
When I open up the Request Handlers dialog I should see my Subscription Handler set to Graphql Over SSE

Steps To Reproduce

Problem manifests when initialSubscriptionRequestHandlerId: "graqhql-sse" with a given query.

Environment

- OS:  Windows
- Browser:   Chrome
- Platform:  ?
- Version: v8.0.5 of altair-static

Additional context

No response

@imolorhe
Copy link
Collaborator

imolorhe commented Dec 15, 2024

Thanks for reporting. I can confirm the issue. Will be fixed in the next release in #2741

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants