fix: handle falsy values for #text/#cdata-section/#comment nodes in toXml

[Copilot]

The falsy short-circuit in toXml fired before the #text/#cdata-section/#comment branch checks, causing nodes like { '#text': '' } to emit <#text /> — invalid XML — instead of correct empty text content.

Changes

• bpmn-elements-adapter/json2xml.ts: Reordered branches in toXml so #text, #cdata-section, and #comment are evaluated before the falsy self-closing guard. The guard now only applies to regular element names.

// Before: empty #text emits invalid <#text />
if (obj !== 0 && obj !== false && !obj) return `${prefix}<${name} />`  // ← fires first
if (name === '#text') return prefix + escapeXml(String(obj))

// After: special names handled first
if (name === '#text') return prefix + escapeXml(String(obj))           // ← correct
if (obj !== 0 && obj !== false && !obj) return `${prefix}<${name} />`

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a363de5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR