Ravi Shankar

As the error says, you should have `"200"` (string) instead of `200` (integer) in responses schema.

The official spec seems to describe the status code as a string (example [here](https://github.com/OAI/OpenAPI-Specification/blob/c5e9a8a703f40da5d5a1a63dc1ff7530263eca4f/versions/2.0.md#responses-object-example)). The JSON schema for v2 spec also says that the [responses schema is an object](https://github.com/OAI/OpenAPI-Specification/blob/c5e9a8a703f40da5d5a1a63dc1ff7530263eca4f/schemas/v2.0/schema.json#L202), which...

Um, no. The `200` should be written as a string in the spec (it will be parsed as an integer, but it should still be `"200"` in the spec).

Okay, I guess it doesn't hurt to deviate a little from the spec and relax the check with an enum of integer/string. This is now open for anyone to work...

Paperclip doesn't have auth support yet, but I do have a plan to work on this before 0.4.0 release (to enforce auth for certain operations at compile time detailed here...

@pickfire I'd love to do that, but it looks like babelfish is a converter for encodings, whereas OpenAPI is a specification which could be in any encoding (JSON/YAML), so this...

> ... just a converter for stuff. Isn't this ambiguous? Either way, it's probably time to update the scope of babelfish in its README and project description. 😄 Paperclip, on...

One other thing I'd like to point out here is that the v2 and v3 spec aren't exactly interchangeable (v2 to v3 is straightforward, but the other way around isn't),...

We do support `#[serde(rename = "...")]`, but tag is something that has to do with enums right? We don't support enums with complex variants as of now, because it can't...

We do support parsing some serde attributes, but we have to support the remaining serde attributes. I don't see another way, sadly 😕