ChilliCream / ChilliCream/graphql-platform

Non buffered data on server from EF core client

Open
#8,950 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Product

Hot Chocolate

Is your feature request related to a problem?

Good afternoon, I need a consultation on your product. We are using your library as a refinement of graphql software. Tell me, do you have support for receiving unbuffered data on the server for the client? We are writing code in C# with EF core integration. ASP.NET and we use query as a streamresult attribute on the method.

Example: [StreamResult] public IAsyncEnumerable getPersons();

We do not want to buffer the data on either the server or the client, but directly send the data received by the graphql query. How would we do this with your library?

Thank you in advance for any response!

The solution you'd like

need a consultation*

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 [StreamResult] getPersons() example and the IAsyncEnumerable return type, then review how the EF Core integration handles result delivery in ASP.NET. Clarify whether unbuffered server and client streaming are both required and define the expected behavior before identifying implementation and test locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.