[bpamiri]

Summary

The telField API example rendered as one long line with visible \n text. Its source, vendor/wheels/public/docs/reference/controller/telfield.txt, was a single line holding literal \n and \t sequences (12 and 5) instead of real newlines and tabs. The docs pipeline copies the file as written.

Source fix: the file now uses real newlines and tabs. The content and # characters are unchanged. Its only runtime reader, $getExtendedCodeExamples, outputs it as display text.

Erratum for the published docs: 4.1.0 and 4.2.0 carry the same example.

• In docs/api/v4.1.0.json and v4.2.0.json, only telField's extended docs value changes; every other entry is identical.
• The two generated pages, web/sites/api/src/content/docs/v4-{1,2}-0/view-helpers/telfield.md, are regenerated from it. Regenerating each version's whole tree otherwise reproduces the committed pages exactly.

Not changed: vitePreloadTag. Its \n appears inside a string that shows the function's output, which is intentional.

Fixes #4620

Testing

• Built the API site. The telField example renders as a 13-line, tab-indented block on both v4-2-0 and v4-1-0, with no visible \n.
• At 390px the page doesn't scroll sideways; the example scrolls inside its block (fix(web): contain wide code examples on API reference pages #4621).
• Each JSON differs from develop in exactly one entry (telField). Only the two telfield.md pages changed.
• vitePreloadTag's page is byte-identical and still renders multi-line.
• No visual baseline change.

🤖 Generated with Claude Code