utopia-gen: Adjust params code to not set nullable on Option for Query params

[Turbo87]

This PR resolves #1215 by ensuring that Option<_> usage in Query params is not transformed into a nullable feature.

https://swagger.io/docs/specification/v3_0/describing-parameters/#default-parameter-values gives an example on how required: false query parameters are described and there is no nullable: true or schema.type: null in there, which indicates that required: false should be sufficient to describe an Option<_> type for query parameters.

(Potentially) Related:

• Query params should not be nullable #1215
• Make Option non-required & add required attr #530
• IntoParams marks Options as required #609
• swagger-ui show request params as required even though they are Options #1058
• Wrapping axum query params makes them required #622

[juhaku]

https://swagger.io/docs/specification/v3_0/describing-parameters/#default-parameter-values gives an example on how required: false query parameters are described and there is no nullable: true or schema.type: null in there, which indicates that required: false should be sufficient to describe an Option<_> type for query parameters.

Although this spec is for OpenAPI 3.0 and not for OpenAPI 3.1.x it is probably right to expect that Option<T> query parameters should not be nullable but only required: false. Except in case of complex query parameters via content but they are not supported as of yet. #620

[Turbo87]

Although this spec is for OpenAPI 3.0 and not for OpenAPI 3.1.x

yeah, unfortunately I couldn't find an equivalent example in the 3.1 spec, but given the validator results in #1215 I guess it's a safe assumption

[juhaku]

Seems solid to me, 👍 Same here just a CHANGELOG.md entry probably under Changed category

[Turbo87]

Same here just a CHANGELOG.md entry probably under Changed category

done :)

[juhaku]

Let's set the ball rolling and merge it to master 🙂