Components.AI: Implement reusable send and stop composer controls
- 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.
Stop is not surfaced and the primary action does not follow the composer and streaming state defined by the target experience.
### Describe the solution you'd like
Provide standalone `SendButton` and `StopButton` parts. Idle text sends; idle empty is disabled; streaming empty shows Stop; streaming text shows Send for a queued follow-up. The controls share one primary slot and never appear together.
### Additional context
Leaf task for #68227 requirements C2, C10, G1, and G3. Queue dispatch behavior is implemented separately.
Contributor guide
Research direction
Start by locating the Components.AI composer implementation and review the requirements referenced in #68227, especially C2, C10, G1, and G3. Trace the existing composer and streaming state entry points, then verify that standalone SendButton and StopButton controls occupy one primary slot and produce the four specified idle and streaming states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100