Skip to content

fix: Pretty print elements with intrinsic values on a single line#296

Merged
Joannis merged 1 commit intoCoreOffice:mainfrom
weppos:fix/pretty-print-intrinsic-values
Apr 9, 2026
Merged

fix: Pretty print elements with intrinsic values on a single line#296
Joannis merged 1 commit intoCoreOffice:mainfrom
weppos:fix/pretty-print-intrinsic-values

Conversation

@weppos
Copy link
Copy Markdown
Contributor

@weppos weppos commented Mar 31, 2026

This PR introduces a fix to the mentioned bug, by keeping elements with intrinsic content encoded via the empty-string CodingKey on a single line when pretty printing.

Fixes #295

Elements using the empty-string CodingKey ("") for intrinsic text
content were being pretty-printed with the value on a separate line:

    <element ref="id">
    120000.0
    </element>

This happened because the pretty printer only checked containsTextNodes,
which isn't set for intrinsic values encoded via keyed containers. Add a
check for elements whose children are all inline (key is empty) and
don't wrap named child elements, treating them the same as text nodes.
@Joannis Joannis merged commit b2b5d72 into CoreOffice:main Apr 9, 2026
3 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pretty-printed intrinsic-value elements are split across multiple lines

2 participants