Marcin Romaszewicz

This is because you are loading a Swagger 2.0 specification, which is different from OpenAPI 3.0. You'll need to convert it before using oapi-codegen on it.

> Hi guys, > > I am getting the following error > > `error generating code: error creating operation definitions: error generating response definitions: error turning reference (#/paths/~1me~1/put/responses/400) into a...

Oh, I agree, but here is my dilemma. Right now, I use kin-openapi's loader to load the spec. It performs things like relative reference resolution via URI when loaded directly...

> I am getting this as well using the Censys API: https://search.censys.io/api/openapi.yml This is an interesting one. `x-partials` isn't a standard top level key under `components` and it has an...

You can install metaz with homebrew, and it works great. You will find homebrew here: https://brew.sh/ Then once you install it, just run "brew cask install metaz"

Looks good overall. I had the mapping so that the instance userdata that the stack created was the same as Amazon's CFN script for EKS workers. I just checked -...

I'm going to punt on this. There are a number of swagger validators out there, and we can just use that as part of and build infrastructure. If you feed...

I use oapi-codegen in this exact scenario, and this authentication logic doesn't need to go into the generated code, `openapi3filter` handles it just fine. It'll evaluate the boolean combination of...

The generator doesn't have enough context to make an authorization decision for you entirely, this will always be a runtime check for your own code, with the aid of generated...

Yeah, exactly. The embedded spec is 100% guaranteed to be in-sync with your code and middleware should use it. It never even occurred to me that people wouldn't set this...