Components.AI: Validate attachments and expose configurable limits
- 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.
Oversized files throw from `OpenReadStream`, type constraints are not enforced server-side, and count/size/type limits are hardcoded or absent.
### Describe the solution you'd like
Add configurable maximum size, count, and allowed types with authoritative validation. Rejected attachments remain visible in a localized failed state, are excluded from sending, and never block otherwise valid submission.
### Additional context
Leaf task for #68227 requirements D1-D2.
Contributor guide
Research direction
Start with the Components.AI attachment implementation and the requirements in #68227, especially D1-D2. Trace the OpenReadStream path and current submission handling, then verify configurable count, size, and type limits, localized failed-state visibility, exclusion of rejected files, and successful submission of valid attachments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100