ContentTypeParser.remove, does not throw if parser does not exist

[Uzlopak]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the issue has not already been raised

Issue

I find it quite inconsequent, if the remove method of ContentTypeParser in case it is not a string or RegExp throws a FST_ERR_CTP_INVALID_TYPE-error but not an Error if there is no parser matching the contentType.

Imho the else case of this if-condition should throw an Error

fastify/lib/contentTypeParser.js

Line 152 in 897360a

if (idx > -1) {

[climba03003]

I am not sure if it should be a bug or something that should fix.
Does anyone really care about if the content-type that should be remove is not exist? If not, throwing shouldn't be a good DX either.

[RajPabnani03]

@climba03003 Yes it Matters if the content-type is available or through error when the value on removal is not equal to NULL !!!

[climba03003]

You say it matters.
But I don't see the later part of the comment show how does it matter.

[kamilogorek]

It's really hard to spot the typo in the content type parser that you want to remove, as the input there is a raw string.