| name | about | title | labels | assignees |
|---|---|---|---|---|
Bug report |
I'm eager to fix your problem... but only if it's my problem 🙃 |
Low quality / low effort issues make me grumpy and cause me to respond in ways I'm not proud of. So let's avoid that unpleasantness by having you do the following:
- If your issue is related to a specific MIME type / extension, please verify the problem doesn't originate in the mime-db project (where this project gets it's data from)
- Make the title descriptive, specific to your problem, and SEO-friendly.
- If your issue involves an error message or stacktrace of any sort, PROVIDE AN MRE
I cannot emphasize that last point enough. A stacktrace or error message by itself is rarely helpful. You must include an MRE in one of the following forms:
| 🙂 Acceptable | Code and instructions for reproducing the problem attached to your issue |
| 😃 Better | Code and instructions in a public repository |
| 🥳 Best | Project on a sandbox service such as StackBlitz, CodePen, or CodeSandbox |
"I don't have time to read that MRE article"
"I don't have time to make an MRE"
"I don't know how to make an MRE"
"Making an MRE is hard"
Then don't bother creating an issue.