Components.AI attachment pipeline
- 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.
Attachment validation, state, acquisition, transfer, and cancellation are currently incomplete and tightly coupled in `MessageInput`.
### Describe the solution you'd like
Track independently mergeable attachment-pipeline tasks under the attachments/media/voice workstream: configurable validation, accessible stateful chips, drag/drop and optional paste acquisition, and scalable transfer/progress/cancellation.
### Additional context
Capability epic under #68227 covering D1-D8.
Contributor guide
Research direction
Start with the MessageInput attachment handling described here and review capability epic #68227 for the D1-D8 scope. Break the work into independently mergeable tasks covering validation, stateful chips, acquisition, transfer, progress, and cancellation; completion criteria are not specified beyond those areas.
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
- Needs clarification
- Newbie friendliness
- 30/100