Redocly removing string for enums if there's non-numbers mixed in

[sthilaire1]

Describe the bug
In my yaml file I have a list of enums of type string. When I bundle my common file using redocly-cli, which outputs the enums onto my common file, it is removing the string if there's non-numbers like "B" mixed in.

Example of my yaml file:
Example from my common file:

To Reproduce

Create a yaml file of mixed integers, like shown in the picture. For instance, "01", "6B".
redocly bundle -o common-api.yaml api-spec.yaml
git add common-api.yaml

Expected behavior
I expect my enum to still be of type string. It should not be turning into an enum or integer?

Logs

OpenAPI description

Redocly Version(s)

1.12.2

Node.js Version(s)

v20.9.0

Additional context

[tatomyr]

Hi @sthilaire1, your enum is still of type string as 6B is not an integer 🙂. In fact, it's a valid string representation in yaml format (you can omit quotes if a scalar is not a number, boolean, null &c.).
I'm closing this, but feel free to ping me if you think I'm missing something here.

[sthilaire1]

Hi Andrew, When the yaml is uploaded to Swagger will it still be of string type? The issue we were thinking was it may not show up like the other enums when uploaded to Swagger. Thanks! Sent from my iPhoneOn May 23, 2024, at 12:51 PM, Andrew Tatomyr ***@***.***> wrote: Hi @sthilaire1, your enum is still of type string as 6B is not an integer 🙂. In fact, it's a valid string representation in yaml format (you can omit quotes if a scalar is not a number, boolean, null &c.). I'm closing this, but feel free to ping me if you think I'm missing something here. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[tatomyr]

will it still be of string type?

@sthilaire1 yes it will. You can try converting that yaml into json in any converter to verify the type.