NickFitton / NickFitton/FortSprite
Set Override image upload and storage lifecycle policy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Question
What upload policy should the Override catalogue enforce for administrator-provided Sprite Variant images, including allowed MIME types and file limits, server-side validation, attachment failure handling, replacement behavior, and cleanup of orphaned or superseded Convex File Storage objects?
Contributor guide
No contributing guide indexed for this repository
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 tracing the Override catalogue's Sprite Variant image upload path and its Convex File Storage integration. Define the required MIME types, file limits, validation and failure behavior, then document replacement and orphan cleanup rules; done means the policy is agreed and implementable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100