Ravi Shankar

No, because that doesn't respect swagger schema and the spec emitted by us may be misinterpreted by other language-specific tools (including the official Swagger UI). So, it's actually better to...

Yeah, we can't do this at the moment because v2 doesn't support it. We'll need v3 (which will be part of 0.5.0 release). If you have spare time to work...

It is. For now, we only have actix-web plugin. When we support other frameworks in the future, we can open related issues.

The proc macros that we have right now implement the traits exposed by the plugin, so they are specific to actix web. Am I addressing this correctly?

No worries! Feel free to ask as many questions as you like! I was just wondering whether I understood and addressed the question correctly. :sweat_smile:

I already have a `GITHUB_TOKEN` env variable with `public_repo` scope for deploying documentation. Could that be used for tags too?

That's correct. The structures and tests for (de-)serializing v3 spec should be easy enough, but the actual conversion may be complicated, so let's just focus on v2 to v3 in...

Sorry, somehow missed this. > What I mean is, keep the proc macros and the traits we currently have but make different modules v2 and v3 to generate different specs....

OpenAPI v2 vs v3 is pretty much the Python 2 vs 3 problem - the only difference is that v2 hasn't reached EOL and people are still using it. I...

I do have this in mind! :smile: