Make Content-Type json validation less rigid so it works with things like application/manifest+json (Fixes #983) #984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is it?
Description
There are Content-Types that are variations of
application/json, likeapplication/manifest+json, which is needed to output a route like/manifest.webmanifest.ts. This PR make it less rigid so it works with those variations.Use cases and why
Using
routes/manifest.webmanifest.tsneeds to printapplication/manifest+json.application/ld+jsonand other variations.Checklist: