ChilliCream / ChilliCream/graphql-platform

Subscription on blazor wasm client does not work with SSE protocol

Open
#6,944 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🌶️ strawberry shake Area: Subscriptions
Dominant language
C#
Stars
5.8k
Forks
810
Avg merge
15h 39m
Merged PRs (30d)
98

Description

Product

Hot Chocolate + StrawberryShake

Version

13.7.1-preview.1

Link to minimal reproduction

https://hotchocolategraphql.slack.com/archives/CMUJ40EHJ/p1707412454351829

Steps to reproduce
  1. Blazor Wasm Client with strawberryShake.blazor installed;
  2. Api with a dummy subscription+mutation with HotChocolate (13.7.1-preview.1);
What is expected?

The information should be returned to the blazor wasm client when the subscription is triggered.

What is actually happening?

On the bcp the subscription/mutation works fine, but on the blazor client the subscription only returns information when i disconnect the api.

Relevant log output

No response

Additional context

This issue was already discussed in the slack channel, tested and confirmed by Michael that it's a bug.

https://hotchocolategraphql.slack.com/archives/CMUJ40EHJ/p1707598377880879

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the minimal reproduction linked in the issue and the Blazor Wasm client using strawberryShake.blazor against the Hot Chocolate API. Reproduce the dummy subscription and mutation over SSE, then trace why results arrive only after the API disconnects. Done means subscription data reaches the client when the subscription is triggered while the API remains connected.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, wasm
Domain
api, frontend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.