Depreciate & remove `mimetype`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
I don't think that mimetype is used by any tooling, and it generally confuses people about what to enter for it and what it will be used for.
The initial idea was that it could help 3rd party tooling for having generators - eg. if the mimetype is text/csv then a spreadsheet editor could be displayed for creating data. If it was text/json then a code editor and so on. However, in practice it's easy and arguably more robust to do this by using filename extension, plus no-one has added editor support anywhere (that I'm aware of).
As such, in order to keep the schema lean and not confuse people, proposal is to drop the field.
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
Search the repository for mimetype to identify its schema definition and every tooling reference. Remove the field from the schema and update the affected checks or documentation, then run the relevant test suite to confirm the schema remains valid and no supported tooling still depends on it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100