openapi

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

I generate swagger for a post method with request body
but the method message has no "parameters.schema.description " field when I set the option " json_schema.description" for the message

To Reproduce

(Write your steps here:)

1. this is my protobuf

<img width="734" alt="image" src="https://user-images.githubusercontent.com/38717535/168068152-6b95bf7b-4bd3-4d85-

Is your feature request related to a problem? Please describe.

Recently noticed how many PHP based projects migrates from Travis-CI to GitHub Actions. I didn't try it yet, but after a quick reading I see that GitHub Actions has Ubuntu environment with preinstalled PHP from 7.4 to 8.1, while Travis CI offers [Bi

springfox-swagger2: 3.0.0-SNAPSHOT
springfox-swagger-ui: 3.0.0-SNAPSHOT
springfox-spring-webflux: 3.0.0-SNAPSHOT

We are using directModelSubstitute for MonetaryAmount to avoid showing all the properties of the class in swagger. Instead of that we created our own MonetaryAmountWrapper which have only two fields viz., amount and currency with some default example values for both. Now, the

The Calling REST APIs section demonstrates how to use LoopBack 4 to call GET APIs. It would be benefiting to the broader community to demonstrate how to call POST APIs. I have the todo-jwt example hosted in Heroku that could be used in the doc

I propose to remove the pass_context_arg_name argument and fix the name under which the context is passed. This parameter is passed often between internal functions and classes, which is not worth the benefit of having it configurable.

I'm using https://github.com/Artory/drf-hal-json/ that basically provides custom base serializers that add dynamically fields like _links into the response via the to_representation method.

I tried to somehow get that into the schema as well, but I'm getting stuck. Are there any directions on what I need to provide/subclass/overwrite, so to make it work?

I imagine I could inspect my seri

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.