🔬 Move MIME types to their own internal library

[jadudm]

At a glance

In order to keep data consistent
as a developer
I want my MIME types to be const/enum

Acceptance Criteria

We use DRY behavior-driven development wherever possible.

then...

Beta Give feedback

1. [a thing happens]

Shepherd

• UX shepherd:
• Design shepherd:
• Engineering shepherd:

Background

The MIME types are a mess. They're in the util library, and sometimes they're strings, and sometimes they're not.

They can be made consistent by creating an enumeration for the types the application uses, and some functions to convert to/from that representation. (E.g. for turning complex representations into canonical ones.)

This is a straight-forward refactoring, but it is scattered all over the code.

Security Considerations

Required per CM-4.

None.

---

Process checklist

• Has a clear story statement
• Can reasonably be done in a few days (otherwise, split this up!)
• Shepherds have been identified
• UX youexes all the things
• Design designs all the things
• Engineering engineers all the things
• Meets acceptance criteria
• Meets QASP conditions
• Presented in a review
• Includes screenshots or references to artifacts
• Tagged with the sprint where it was finished
• Archived

If there's UI...

• Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
• Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
• Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.