Is your feature request related to a problem? Please describe.
Currently, when the schema of a response body includes the enum field, the Developer Portal renders the column Type as enum and discards the type in the schema. Example: endpoint Get list of the possible facets for a given query (print).
Describe the solution you'd like
It would be nice if our UI could show both information, enum and type.
Describe alternatives you've considered
The UI could show both values side by side, as in enum | string or string | enum. Similar to nullable fields: string | null.
Additional context
None, thanks.
Is your feature request related to a problem? Please describe.
Currently, when the schema of a response body includes the
enumfield, the Developer Portal renders the column Type asenumand discards the type in the schema. Example: endpoint Get list of the possible facets for a given query (print).Describe the solution you'd like
It would be nice if our UI could show both information,
enumand type.Describe alternatives you've considered
The UI could show both values side by side, as in
enum | stringorstring | enum. Similar to nullable fields:string | null.Additional context
None, thanks.