feat(ajv): add returnsCoercedValues option to keep the coerced value by ajv

[EinfachHans]

Information

Type	Breaking change
Fix	No ?

---

closes #2497

With this PR the result of a Validation is correctly returned. The resulted data can be different from the input data, when the validation modifies it, which is a common usage.

This is my first PR to this awesome project. Please let me know if i'm missing something 🤔

Todos

• Tests
• Coverage
• Example
• Documentation

[Romakita]

@EinfachHans thanks for the PR. Just a small change to optimize the code ;)

see you

[EinfachHans]

@Romakita okay somehow an integration test is now failing. Didn't know why it worked locally first...

Anyways, the test that fails is Scenario8 in testBodyParams.ts, which tests a null model input should return the null model back. I'm unsure about this test, can you have a look?

[Romakita]

Yes I take a look. This test is here to check if the null value is keep through after validation and deserialization depending on the endpoint configuration.
This one of the side effect of ajv.
I’ll check if it’s pertinent or not.

[Romakita]

Ok I already given information on this issue and why isn't fixable easily:
#2355

[EinfachHans]

Mhh, so should i close this PR?

[Romakita]

@EinfachHans I fixed the problem by introducing a new ajv options returnsCoercedValues.

Can you review the latest commits please ;)

[Romakita]

This PR will solve your issue and another issue related to the coerced value by ajv! Good news :D

[EinfachHans]

@Romakita awesome, Thanks! 🚀
Code makes totally sense and documentation is quite clear or me 👍🏼

[Romakita]

Ok fixed issue on my local. It should be ok to merge and release after that ;)

[Romakita]

🎉 This PR is included in version 7.43.0 🎉

The release is available on:

• v7.43.0
• GitHub release

Your semantic-release bot 📦🚀