fix(schema): simplify json-schema when Nullable is used with only one primitive type

[Romakita]

Close: #2751

Information

Type	Breaking change
Fix	No

---

Todos

• Tests
• Coverage
• Example
• Documentation

[github-actions]

Benchmarks

• Machine: linux x64 | 4 vCPUs | 15.6GB Mem
• Node: v18.20.3
• Run: Mon Jul 15 2024 22:00:10 GMT+0000 (Coordinated Universal Time)
• Method: autocannon -c 100 -d 10 -p 10 localhost:3000 (two rounds; one to warm-up, one to measure)

	Version	Router	Requests/s	Latency	Throughput/Mb
koa	2.13.4	✗	33630.4	29.21	6.00
tsed-koa	7.75.4	✓	11996.0	82.58	10.16
express	4.19.2	✓	10528.0	94.06	1.88
express-injector	4.19.2	✗	9728.2	101.75	2.22
nest	8.4.3	✓	9462.4	104.77	2.27
tsed-express	7.75.4	✓	8801.8	112.55	1.61
express-morgan	4.19.2	✗	5644.4	175.27	1.01
fastify-big-json	3.29.4	✓	N/A	N/A	N/A
fastify-injector	3.29.4	✓	N/A	N/A	N/A
fastify	3.29.4	✓	N/A	N/A	N/A
nest-fastify	8.4.3	✓	N/A	N/A	N/A

Explanation

The benchmark shows a performance difference between the frameworks. We note that Ts.ED is often last. In fact, Ts.ED uses features useful to a production application which reduce its performance.

For example, Ts.ED initializes a sandbox (async_hook) for each request in order to work in an isolated context if necessary.
It also initializes the elements necessary for monitoring requests in a log manager.

All this at a necessary cost that reflects the reality of a production application ;)

[Romakita]

🎉 This PR is included in version 7.75.5 🎉

The release is available on:

• v7.75.5
• GitHub release

Your semantic-release bot 📦🚀