xml-doc-description-sanitization

To fix JSON-escaped Unicode in OpenAPI generated XML documentation, you must decode JSON escape sequences like \uXXXX before injecting the text. This process ensures API descriptions are safely embedded into XML comments without losing readability.

The best way to escape XML-reserved characters in API descriptions is to apply a sanitization filter that converts symbols like &, <, and > into valid XML entities. This maintains valid XML structure while preserving the original text meaning.

XML doc sanitization handles intentional markup by applying decoding and escaping exclusively to API-sourced descriptions. It includes safeguards to avoid altering hardcoded XML markup, ensuring intentional tags remain intact during the sanitization process.

Yes, you can preserve Unicode characters when generating code from OpenAPI definitions by decoding JSON-style escape sequences before inserting the text into XML documentation comments. This prevents character loss during the code generation workflow.

Your XML documentation comments break because OpenAPI response descriptions often arrive JSON-escaped with characters like \n or \uXXXX. If these are not decoded and XML-reserved characters are not escaped, the resulting XML structure becomes invalid.