dotnet / dotnet/aspnetcore

Components.AI: Preserve composer drafts across transitions and conversation switches

Open
#68,404 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: M feature-blazor-state-preservation Priority:2
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.

Typed input can be lost across render-mode transitions or when moving between conversations.

### Describe the solution you'd like

Define and implement draft identity and lifetime so each conversation restores its text and applicable composer state across switching and render-mode transitions without silently losing user input.

### Additional context

Leaf task for #68227 requirement C7. Relates to conversation-switch semantics.

Contributor guide

Open the contributing guide

Research direction

Start by reading requirement C7 in issue #68227 and the related conversation-switch semantics. Locate the Components.AI composer entry point, then define how draft identity and lifetime should work across conversation switches and render-mode transitions; done means text and applicable composer state are restored without silent loss.

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
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.