Contributing to MimeTypes.NET

Thanks for contributing! This guide covers everything you need to add new MIME types or fix existing ones.

Adding MIME types

Each MIME type category lives in its own file under MimeTypes/:

Add your constant in alphabetical order within its class, following this pattern:

/// <summary>
/// image/jp2
/// </summary>
public const string Jp2 = Prefix + "jp2";

The XML doc comment is to provide richer contextual information for users, e.g. in IDE hover text.

Constant names MUST reflect the MIME type subtype rather than be descriptive (e.g. image/jp2 → MimeType.Image.Jp2, not MimeType.Image.Jpeg2000).
Constant names MUST use PascalCase, in line with standard C# naming conventions.
Punctuation characters such as +, . and - MUST be omitted and treated as a word break for PascalCase naming purposes (e.g. svg+xml → SvgXml, vnd.microsoft.icon → VndMicrosoftIcon).
A digit at the start of a subtype name MUST be substituted with its English spelling (e.g. 3gpp -> Threegpp).

Every constant MUST have a corresponding test in MimeTypes.Tests/. Add a [TestCase] line to the appropriate test file:

[TestCase(MimeType.Image.Jp2, "image/jp2")]

Tests verify that the constant value exactly matches the expected MIME type string.

Please reference an RFC or other authoritative source for the MIME type(s) you're adding in your PR description.

dotnet test

Constants are named to match the MIME type value (not a descriptive name)
Constants are in PascalCase
Constants are in alphabetical order within their class
Each new constant has an XML doc comment
Each new constant is covered by a test case
Each new constant is covered by an RFC or other authoritative source cited in the PR description
100% tests passing