Ajv 'coerceTypes' option should probably not be set for request bodies about exegesis

[jwalton]

Yeah, you are correct. We should make coerceTypes an option. We probably need to leave it turned on for parameters (or do some type coercion ourselves) since parameters are always going to get parsed as strings (which is why I turned it on in the first place) but it shouldn't be on for bodies.

We might even want to make it optional based on the mime type of the body; you would generally want it turned off for JSON (because the type is not ambiguous in JSON), but in multipart/mixed or application/x-www-form-urlencoded, you'd still want type coercion... OR, maybe instead of making it optional, it should be up to the body parser - so the JSON body parser would not do type coercion, but other body parsers might.

[jwalton]

🎉 This issue has been resolved in version 1.4.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀