The list of supported mime-types is too limited
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
Now I see the list of supported mime-types:
```kotlin
enum class MimeType(val mimeText: String, val isBinary: Boolean, val extension: String) {
PLAIN("text/plain", false, "txt"),
HTML("text/html", false, "html"),
CSS("text/css", false, "css"),
PNG("image/png", true, "png"),
APNG("image/apng", true, "apng"),
GIF("image/gif", true, "gif"),
JPEG("image/jpeg", true, "jpeg"),
BMP("image/bmp", true, "bmp"),
WEBP("image/webp", true, "webp"),
JS("application/javascript", false, "js"),
JSON("application/json", false, "json"),
XML("application/xml", false, "xml"),
ZIP("application/zip", true, "zip"),
GZIP("application/gzip", true, "gzip");
}
```
And they are too few. In practice many more file types are used including ttf, md, etc. They are hundreds. So, the enum here looks inappropriate.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the MimeType enum shown in the issue and inspect all of its usages to understand how MIME types are selected and consumed. Define the required replacement scope and verify that common file types such as TTF and Markdown can be handled without the current enum's limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100