dotnet / dotnet/aspnetcore

Components.AI decorators and conversation actions

Open
#68,376 0 comments 0 reactions 0 assignees View on GitHub
area-blazor feature-blazor-builtin-components
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

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

Components.AI has no reusable seam for per-message or per-turn decoration, preventing built-in and app-supplied actions from composing consistently.

### Describe the solution you'd like

Track API design and implementation of separate message and turn decorators, optional placement merging, accessible visibility and traversal, built-in action menus, copy/retry/edit actions, timestamps, and feedback.

This is a workstream under #68227. Its independently mergeable tasks are represented as native sub-issues.

### Additional context

Covers D4, D13, and F1-F10 from #68227.

Contributor guide

Open the contributing guide

Research direction

Start with the parent design work in #68227 and review the native sub-issues linked from this workstream. Choose an independently mergeable task covering the listed decorator, action, accessibility, timestamp, or feedback areas; this issue itself does not identify a file, test, or single completion target.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
ai, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.