Feature Request: response vs responses

[do-not-do-that]

serverless version : 3.0.0
serverless-auto-swagger version : 2.12.0

I expected to be able to clearly use the parameters already configured by serverless through the issues below.
Other things seem to be fine, but the response creates an issue.

#21

• serverless http response

response?: {
  contentHandling?: "CONVERT_TO_BINARY" | "CONVERT_TO_TEXT";
  headers?: {
    [k: string]: string;
  };
  template?: string;
  statusCodes?: {
    [k: string]: {
      headers?: {
        [k: string]: string;
      };
      pattern?: string;
      template?:
        | string
        | {
            [k: string]: string;
          };
    };
  };
};

• serverless-auto-swagger response

responses: {
  200: {
    description: "test",
  },
},

I don't want to ruin my type system. (I need to change the type to any to use swagger) Can you change the response to response similar to the parameters supported by serverless, and format it?

If the formatting is correct, I will be less confused when defining parameters in one place and writing code.