openapi3

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Base64 packing the logo is unproductive and prohibitively complicated.

Originally I just thought it was related to the method of delivery, minification,etc....

But then I discovered the "enterprise" copy you sell directly offers the "feature" of changing the logo, which then just packs up a new image.

Now I realize why changing the logo is difficult and you won't document how to do it in

Bug Report Checklist

• [~] Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator, yes I used the validate function of the api generator
• [5.0.0 ] What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?

Schemas, Operations, support Swagger extensions. Rather than inferring Go type names from those properties, we can also allow specifying them. Adding support for an extension like x-go-typename on those would allow for more flexibility in naming the Swagger properties more clearly since they don't have to map to the same Go type.

While not technically in violation of the OpenAPI specification, including a query parameter in a path should be flagged as an error in Spectral:

A path has specific meaning in HTTP as a part of a URL that comes after the host name and before the query string or fragment. A "path item" key must be only a path, it cannot have a query string or a fragment.

For example, the following when def

This might be helpful - too many redirects may be considered an error. E.g. the API schema might need to provide endpoints that won't involve any redirection at all, for example, if the app redirects "/api/users" to "/api/users/", then the schema should have endpoints with trailing slashes to avoid these redirects for clients at all.

Implementation notes

• Update models.Case.call signatu

I had opened an issue in the Shins project along these lines, but felt it might be better(?) considered here. Mermade/shins#53

To state the scenario from that issue:
Once a user is logged into our site, I'd like to be able to inject a user's API key dynamically into the API calls within the documentation. I'm using Widdershins to generate the base docs from OpenAPISp

• https://dzone.com/articles/apis-with-nodejs-and-express-automatically-validat

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene