Asking here because I know reitit does swagger…
I’m guessing both going from /foo/bar
into /foo/{bar}
and the reverse of /foo/{bar}
into /foo/bar
in swagger/openapi-v3 are breaking changes for clients? Is there a way to write yaml definitions such that they can grow? i.e. is it valid to have both definitions listed, and will clients fall through to definitions that match?
Does anyone know where these semantics are discussed?
It’s ok I’ve found it: https://spec.openapis.org/oas/v3.0.3#path-templating-matching