dotnet / dotnet/aspnetcore

Components.AI: Implement the extensible rich-node renderer

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

Description

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

`RichContentBlock.Content` is ignored and only raw text is emitted.

### Describe the solution you'd like

Implement the approved renderer to walk supplied rich-content trees, render supported nodes, invoke per-kind extension points, preserve stable node identity, and update incrementally during streaming without replacing completed DOM.

### Additional context

Leaf task for #68227 requirements J2 and J6. Depends on approved renderer API and scoped streaming renders.

Contributor guide

Open the contributing guide

Research direction

Start by reading the approved renderer API and the scoped streaming renders referenced by this issue, then review requirements J2 and J6 in #68227. Done means supported rich-content trees render through per-kind extension points, node identity remains stable, and streaming updates do not replace completed DOM.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.