Inconsistent rendering of schema titles, refs, and types across UI elements · Issue #5649 · scalar/scalar · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating API documentation with Scalar for an OpenAPI 3.1 spec, different UI elements display different schema identifiers: sometimes the title, sometimes the component key (ref), and sometimes the raw JSON type (object/array). This inconsistency is confusing for end users.
Define an OpenAPI document with a schema whose components.schemas key differs from its internal title.
Reference that schema (or use it in a oneOf with a discriminator) in a path operation.
Generate the docs with Scalar.
Observe:
Left sidebar (Models) and section headers show the schema’s title.
Field type labels (e.g. object, array SubModel__Schema_Ref[]) use the JSON type or the component key.
“Show …” links for nested schemas again display the title.
What did you expect to happen?
All UI elements should consistently use the same identifier—ideally the human-readable title—or clearly distinguish between “Type”, “Schema Ref”, and “Schema Title” with explicit labels.
Uh oh!
There was an error while loading. Please reload this page.
What happens?
Describe the bug
When generating API documentation with Scalar for an OpenAPI 3.1 spec, different UI elements display different schema identifiers: sometimes the
title
, sometimes the component key (ref), and sometimes the raw JSON type (object/array). This inconsistency is confusing for end users.Sandbox link
To Reproduce
components.schemas
key differs from its internaltitle
.oneOf
with adiscriminator
) in a path operation.title
.object
,array SubModel__Schema_Ref[]
) use the JSON type or the component key.title
.What did you expect to happen?
All UI elements should consistently use the same identifier—ideally the human-readable
title
—or clearly distinguish between “Type”, “Schema Ref”, and “Schema Title” with explicit labels.Screenshots
OpenAPI Document
https://sandbox.scalar.com/e/aW4Rr
The text was updated successfully, but these errors were encountered: