Skip to content

We need a solution for API Explorer + Custom ModelBinder #4825

Open
@rynowak

Description

@rynowak

see: aspnet/Mvc#5673 (comment) and domaindrivendev/Swashbuckle.AspNetCore#309

The complaint here is that we 'expand' a parameter in the API definition that's being bound by a custom model binder. API explorer has no interaction with model binders/providers, and so no way to know that this isn't being handled by the default binder.

In this case we already have a metadata feature that would give the desired API explorer output, ModelMetadata.IsComplexType == false. However we don't allow user code to configure this value.

We should either make this configurable, or probe the model binders for information about types that have custom handling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: DesignThis issue requires design work before implementating.affected-fewThis issue impacts only small number of customersarea-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-openapiseverity-majorThis label is used by an internal tool

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions