UFileUpload: ability to use custom file types and further flexibility improvements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.1k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 57
Description
Package
v4.x
Description
Currently the capabilities are severely limited to using a File instance as a model value. If we need to "update" files (for example, some files are URLs, while others are actual File's), which is pretty common use-case (e.g. avatar, product images etc), the current implementation doesn't provide a way to do so. This is also impossible with slots as they check for the presence of items and prevent the slot from rendering if they don't exist.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the UFileUpload implementation and tracing how its model value is restricted to File instances and how slots check for items. Determine the existing tests or component entry points for these behaviors. Done should allow mixed URL and File values, support custom file types, and preserve flexible slot rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100