dotnet / dotnet/aspnetcore

Components.AI: Scope streaming renders to the changing message

Open
#68,389 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-blazor-builtin-components Priority:0
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 6h
Merged PRs (30d)
290

Description

### Is your feature request related to a problem? Please describe the problem.

Every streaming block update currently re-renders the full message list, causing unnecessary work and unstable DOM behavior.

### Describe the solution you'd like

Update the rendering boundaries so only the affected message/block re-renders during streaming. Already completed turns and messages must retain component and DOM identity.

### Additional context

Leaf task for #68227 requirements A3 and J6. Requires stable turn/message/block identity.

Contributor guide

Open the contributing guide

Research direction

Start by reading requirements A3 and J6 in #68227, then locate the Components.AI streaming render path. Trace how turn, message, and block identity are handled during updates. Done means only the changing message or block re-renders while completed turns and messages retain component and DOM identity.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.