Matteo Collina

icon indicating a website link nodeland.dev icon indicating an email [email protected]

icon company @platformatic icon location Forlì, Italy icon location @platformatic Co-Founder & CTO, TSC member @nodejs, Lead Maintainer @fastify, Conference Speaker, Ph.D.

Results 3442 comments of Matteo Collina

OAS 3.1: Examples in the open api spec schema property should be an array

cc @mxck

OAS 3.1: Examples in the open api spec schema property should be an array

All of you are significantly more expert than me on the OpenAPI spec. I defer to contributors on these OAS features

OAS 3.1: Examples in the open api spec schema property should be an array

To clarify: OpenAPI v3.1 has some breaking changes compared to v3.0 on the examples property?

OAS 3.1: Examples in the open api spec schema property should be an array

What other differences are there between OAS 3.0 and 3.1? We should add support to OAS v3.1 too but keep the v3.0 line as-is. Would you like to give it...

OAS 3.1: Examples in the open api spec schema property should be an array

We differentiate with an option to the plugin, check with how swagger vs oas are handled.

Have the render function for dirlist work for json as well

Would you like to send a Pull Request to address this issue? Remember to add unit tests.

Have the render function for dirlist work for json as well

Go for it!

inconsistent application of `encodeUri`

I don't understand what is the ask or problem. Reserved characters in uri MUST be percent-encoded (it's the spec). How does it break your app? Could you write a code...

inconsistent application of `encodeUri`

It might be that a different/better fix for https://github.com/fastify/fastify-static/issues/143 is possible, something that does not break normal usage. Would you like to give it a go and send a PR?

inconsistent application of `encodeUri`

Thanks!