feat: rendering the syntax of different content types responses

[iifawzi]

Signed-off-by: iifawzi [email protected]
resolving #117

As per fastify/fastify#4264, swagger should support different content types responses.
Tests here will fail until the feature is merged at fastify, but I've hard-codded the fastify proposed changes and tested it.

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[Eomm]

Tests here will fail until the feature is merged at fastify, but I've hard-codded the fastify proposed changes and tested it.

You can change&push temporary the package.json to use your fastify branch:

    "dependencies": {
        "fastify": "github:iifawzi/fastify#supporting-different-content-types"
    }

so we will check the green ci

[iifawzi]

Tests here will fail until the feature is merged at fastify, but I've hard-codded the fastify proposed changes and tested it.

You can change&push temporary the package.json to use your fastify branch:

    "dependencies": {
        "fastify": "github:iifawzi/fastify#supporting-different-content-types"
    }

so we will check the green ci

Nice to know, committed.

[zrosenbauer]

Fix the misspelling please 😄

[Uzlopak]

Suggested change

	Please use `content` for the response otherwise Fastify itself will fail to compile the schema:
	Use `content` for the response otherwise Fastify itself will fail to compile the schema:

Nothing to please here ;)

[iifawzi]

Please is used everywhere in the readme

[iifawzi]

I don't mind removing it though

[iifawzi]

since fastify/fastify#4264 is finally finished :D, CI should be green here, and then can be merged

[mcollina]

lgtm

[iifawzi]

committed @Uzlopak suggestions, and temporarily updated the packages to check ci.

[mcollina]

Fastify v4.9.0 shipped.

[mcollina]

lgtm