Where are schemas being generated.

Q&A (please complete the following information)

• OS: Windows 10
• Browser: Chrome
• Version: 2.something? whatever swashbuckle 4.1 uses
• Method of installation: packaged with swashbuckle
• Swagger-UI version: [e.g. 3.10.0]
• Swagger/OpenAPI version: OpenAPI 3.0

Content & configuration

Swagger-UI configuration options:

SwaggerUI({
        var configObject = JSON.parse('%(ConfigObject)');
        var oauthConfigObject = JSON.parse('%(OAuthConfigObject)');
        // Apply mandatory parameters
        configObject.dom_id = "#swagger-ui";
        configObject.presets = [SwaggerUIBundle.presets.apis, SwaggerUIStandalonePreset];
        configObject.layout = "StandaloneLayout";
})

How can we help?

I am trying to create a plugin that will, in a hack-ey way, probably ignoring the current open API 3.0 spec, create a poly-morphic array of objects. when the json is sent to swagger-ui, it is parsed down in to the "spec" object. what I want to know where exactly are the "schema" objects for each "definitions" being generated from the spec object. for example this is a snippet from my json.

and the actual reference.

so what I'm expecting is that when the schema object is created, which from what I understand is the object that will be displayed in the ui, will contain the description from the property level and the rest of the information in the actual reference. what I end up with while debugging is something like this...

this is a snippet from the model component in the render method for schema.

so for whatever schema is being passed into the model, I want to know where I can override the schema generating behavior for my plugin. I am having a doozy of a time finding this for some reason. thank you in advance.

Start by reading the model component's render method and tracing the schema passed to it from the parsed spec object, including definitions and references. Investigate whether Swagger UI exposes a plugin extension point for schema generation or overriding this behavior. The issue is done when the relevant entry point and supported customization path are identified.