Allow defining inline object schemas in request/response bodies

[iaminnasr]

Currently, in Apicurio Studio, when defining a request body or response body, it is only possible to reference an existing Data Type (schema) that was created separately under Data Types. This makes it impossible to directly define an inline object (e.g., type: object with properties) within the body definition, even though it's fully supported by the OpenAPI specification.

Example of what is currently not possible in the UI but valid in OpenAPI:

requestBody:
  required: true
  content:
    application/json:
      schema:
        type: object
        properties:
          username:
            type: string
          password:
            type: string

Expected behavior:

When defining a request or response body, users should have an option like “Inline Object” as a schema type.

The UI should allow adding properties directly inside the body without first creating a reusable Data Type.

Usefulness / Justification:

Faster prototyping—no need to switch context to the Data Types tab.

Handy for one-off schemas that don’t require reuse.

Aligns with OpenAPI’s flexibility, supporting both reusable and inline schema styles.

Environment:

Apicurio Studio version: (Beta1)
Deployment: (docker)

[EricWittmann]

Yes, this is definitely a limitation. Thanks for the report.

[EricWittmann]

We haven't had much bandwidth to evolve the OpenAPI editor, so the rough edges remain rough. :(