OpenApi schema field descriptions containing new lines

Hi,

A small possible issue I noticed by accident when testing something.

Say that I have an OpenApi schema that contains something like

"status": {
    "type": "string",
    "description": "pet status\r\nin the store",
    "enum": [
        "available",
        "pending",
        "sold"
    ]
}

Then i get this for the generated type

Which looks like the doc comment has been split over two lines, when I guess it should be collapsed in to one, or have /// on both lines? (fwiw, I have a couple of schemas that are generated from ASP.Net Core services which do that if a comment on the .NET type is multi-line).

Thanks.

[Zaid-Ajaj]

Hi @Numpsy as of latest source, enum types (with enum names), enum flags (without names) and allOf references are handled (for inheritance). Please give it a try and see if I missed something other than oneOf and the client generation

[Zaid-Ajaj]

Hi @Numpsy this should be an easy fix I think. We can split the description over multiple lines.

It would be awesome if you could share the schema you have or an anonymised version of it where you rename fields or remove descriptions. It would make for a good example to test this project with since I don’t have proper sNSwag schema’s to work with.