dotnet/aspnetcore

Additional streaming parameter types

Open

#5,316 opened on Jul 3, 2018

View on GitHub
 (7 comments) (2 reactions) (0 assignees)C# (10,653 forks)batch import
Blazor ♥ SignalRNeeds: Designaffected-very-fewarea-signalrenhancementhelp wantedseverity-nice-to-have

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Currently the user can pass in ChannelReader<T>.

Want to expand this to accept the Stream class, possible the new Pipeline class, etc. Make a common pattern for adding on additional types, maybe somehow tied to IEnumerableAsync.

Contributor guide

Research direction
Investigate how ASP.NET Core currently handles ChannelReader<T> and explore ways to extend support to Stream, Pipeline, and other async enumerable types. Look at existing patterns like IEnumerableAsync and consider a unified approach for parameter binding.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#ASP.NET Core
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40