Preserve Special Characters in Constraint Names for Quality Reports

🚀 Feature Request

Summary

Currently, when using special characters such as < or > in constraint names (e.g., ), these characters are stripped from the Quality Report output. This feature request proposes that special characters in constraint names be correctly retained in Quality Reports.

Problem to Solve / User Story

As a user working with XML-like constraint names, I want the Quality Report to display the exact constraint names including < and > characters, so that I can easily identify which constraints are being referred to and ensure traceability.

Currently, constraint names containing < or > are rendered without these characters and whatever is inbetween in the report, which can cause confusion and make it difficult to match the report to the original constraints. For example, a constraint name like " exists" appears simply as "exists" in the report instead of preserving the original name.

Proposed Solution

Preserving the raw characters in plain text outputs.

Benefits

• Improves clarity and traceability in Quality Reports.
• Avoids ambiguity when reviewing constraint compliance.
• Makes the report consistent with the original constraint definitions.

Possible Drawbacks

Minimal risk of breaking existing report parsing or formatting if not implemented carefully.

Additional Context

This issue primarily arises when XML-style names (like ) are used for constraints. Preserving these characters would maintain consistency between source definitions and generated reports.

Relevant Logs or Screenshots (if applicable)

Requirements or Dependencies

Proper testing for other special characters.

Alternatives Considered

• Using placeholder characters in reports (less readable and not preferred).
• Forbid characters like < and > in Constraint names when creating constraints