open-api

Is your feature request related to a problem? Please describe.
Not really, it's more a better UX when writting your OpenAPI file

Describe the solution you'd like
Like for Object properties, we should be able to give parameters names as key (to avoid duplication)

Additional context
Here is an example before / after this feature:

get:
  summary: Get an Order
  descri

I'm using the version 0.7.2 and my response type is the following case:

public class Response
{
    public string Test { get; set; }
    public Test[] MyProperty { get; set; }
}

public class Test
{
    public int MyProperty { get; set; }
}

The schema for the Test class won't be generated becase of the property with the same name, if we change it to any other name it works

Currently we are just catching (thanks @c-martinez ) errors when we fail to parse query metadata. These are situations in which the parsing will most probably fail:

• Empty line at the beginning of the metadata section
• More than one empty line at the end of the metadata section
• Inconsistent indenting
• Etc.
  At the moment the backend fails silently, and simply no OpenAPI spec is rendered f

This package is wonderful, and I've been having a blast working on prototyping serving some of my org's Swagger definitions with it. One thing I've run into, however, is an inability to use file refs as specified in https://redoc.ly/docs/resources/ref-guide/

This is fairly easily reproduced by opening up the example project in this repo, taking one of the schemas in the components section o

• Return posts' and comments' likes as a number, not an array of likes
• Make an endpoint to fetch users who liked a post
• On the frontend - fetch only the number of likes (for posts and comments), DON'T fetch the users who liked, because there's no view to do that yet