我浏览了springfox的代码，试图找到一些自定义类型解析的入口点，幸运的是，它有一个可以从外部注入的HandlerMethodResolver。
我在我的swagger config类中添加了这个解析器的自定义实现：

@Bean
@Primary
public HandlerMethodResolver fluxMethodResolver(TypeResolver resolver) {
    return new HandlerMethodResolver(resolver) {
        @Override
        public ResolvedType methodReturnType(HandlerMethod handlerMethod) {
            var retType = super.methodReturnType(handlerMethod);

            // we unwrap Mono, Flux, and as a bonus - ResponseEntity
            while (
                    retType.getErasedType() == Mono.class
                    || retType.getErasedType() == Flux.class
                    || retType.getErasedType() == ResponseEntity.class
            ) {
                if ( retType.getErasedType() == Flux.class ) {
                    // treat it as an array
                    var type = retType.getTypeBindings().getBoundType(0);
                    retType = new ResolvedArrayType(type.getErasedType(), type.getTypeBindings(), type);
                } else {
                    retType = retType.getTypeBindings().getBoundType(0);
                }
            }

            return retType;
        }
    };
}

这正是我所需要的。

它会自动将Mono<ResponseEntity<Flux<PartnerDTO>>>转换为PartnerDTO[]，并将Mono<ResponseEntity<Mono<PartnerDTO>>>转换为PartnerDTO。

EDIT：：我更改了这个实现，将Flux转换为T[]，因为它从一开始就应该是这样的。

你也可以按照Sprinfox的例子：

• 声明一个RecursiveAlternateTypeRule.java
• 将其作为alternateTypeRules添加到您的Swagger Configuration

@Configuration
@EnableSwagger2WebFlux
public abstract class AbstractSwaggerConfiguration {

@Autowired
private TypeResolver resolver;

@Bean
public Docket api() {
    return new Docket(DocumentationType.SWAGGER_2) //
        .select().apis(RequestHandlerSelectors.any()).paths(PathSelectors.any()) //
        .build()
        .alternateTypeRules(new RecursiveAlternateTypeRule(resolver,
            Arrays.asList(AlternateTypeRules.newRule(resolver.resolve(Mono.class, WildcardType.class), resolver.resolve(WildcardType.class)),
                AlternateTypeRules.newRule(resolver.resolve(ResponseEntity.class, WildcardType.class), resolver.resolve(WildcardType.class)))))
        .alternateTypeRules(
            new RecursiveAlternateTypeRule(resolver, Arrays.asList(AlternateTypeRules.newRule(resolver.resolve(Flux.class, WildcardType.class), resolver.resolve(List.class, WildcardType.class)),
                AlternateTypeRules.newRule(resolver.resolve(ResponseEntity.class, WildcardType.class), resolver.resolve(WildcardType.class)))));
    }
}

Springfox，看起来是missed the boat。使用springdoc-openapi代替。我们还遇到了springfox的其他问题，不仅缺少webflux支持，而且我们很高兴地切换到了springdoc-openapi
对于webflux应用程序，您所需要的只是添加依赖项springdoc-openapi-webflux-ui：

<dependency>
      <groupId>org.springdoc</groupId>
      <artifactId>springdoc-openapi-webflux-ui</artifactId>
      <version>1.6.9</version>
</dependency>

不需要额外的配置，Mono和Flux将开箱即用。
还有一个如何从springfox迁移到springdoc-openapi的manual。
如果需要以编程方式自定义配置，请按如下方式定义OpenAPI Bean：

import io.swagger.v3.oas.models.OpenAPI;
import io.swagger.v3.oas.models.info.Info;

@Configuration
public class OpenApi30Config {
    @Bean
    public OpenAPI openApi() {
        return new OpenAPI()
           .info(new Info().title("My Application")
                .description("This is my application")
                .version("1.0")
            )
            // and lot of other configuration possible here
            ;
    }
}