Scherma property type "string" gets rendered incorrectly when followed by enum

[DanielaGordas]

Hi @mrin9,

When the property type is string and it is followed by a list of enum the type gets incorrectly rendered in the schema as enum instead of string like in the example below:

Using openapi: 3.1.0

I was wondering if there is any quick fix for this? Thanks in advance!

[mrin9]

this is more of a feature than a bug. When the schema has more than just the type such as enum, format or is it nullable etc, we prefer showing more specific one. This is what we found is desired in most cases.

[DanielaGordas]

Thanks for the quick reply and for the explanation. I can see why that's preferred in many of the cases listed.

Is there any workaround to still display the type as string but also use the enum to list the allowed options?

Thanks!

[mrin9]

there is none at the moment. I have added this question in our next internal user-survey. will keep this issue open for some time for our open source community users to vote/comment on it