Fix structured text translation for soft line breaks, links, and inline blocks

[thales-goncalves]

Summary

• Fixes Structured text spans containing soft line breaks (\n) are silently skipped during translation #77 — text spans containing \n (soft line breaks from Shift+Enter) were silently skipped during translation
• Fixes Plugin translate fails with Structured Text blocks with Inline Blocks #73 — inline blocks and other non-standard node types caused errors

Root causes and fixes

Soft line breaks (#77): getValueType misclassified text containing \n as markdown (matched markdownparagraph regex), and getStructuredTextTranslation only translated PathType.text spans. Fix: check path.key === 'text' instead of path.type === PathType.text.

Node type handling (#73): isStructuredTextText used rigid key-count checks that only matched nodes with exact key combinations (type + children, optionally level/style). Nodes like link (has url), itemLink (has item), and inlineBlock were not recognized. Fix:

• Broadened isStructuredTextText to recognize any node with type + children (excluding blocks, inline items, and code)
• Extended isStructuredTextBlock to also handle inlineBlock nodes
• Added item key to the ID protection list in getValueType

Node types now handled

Node type	Status
softBreak (\n in text)	Fixed — text now translated
link	Fixed — text translated, URL preserved
itemLink	Fixed — text translated, item reference preserved
inlineBlock	Fixed — handled like block
inlineItem	Already worked
block	Already worked

Test plan

• 8 new tests added (105 total, all passing)
• Soft line break text spans are translated
• Link text translated, URLs preserved
• itemLink text translated, item references preserved
• inlineItem nodes preserved without crash
• block nodes preserved without crash
• inlineBlock nodes handled correctly
• All existing tests still pass

[netlify]

✅ Deploy Preview for datocms-plugin-translate-fields ready!

Name	Link
🔨 Latest commit	7caf1c5
🔍 Latest deploy log	https://app.netlify.com/projects/datocms-plugin-translate-fields/deploys/69d7d78ce7fb35000872e60f
😎 Deploy Preview	https://deploy-preview-79--datocms-plugin-translate-fields.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Siilwyn]

🌊 Thanks you for your contribution! I like the concept of this change, but I briefly discussed this with @velomovies and we are afraid this might introduce other bugs regarding field detection.
Instead of duck typing the field types we're thinking of using Dato's schema to handle the different types of fields to translate.
Looks like Dato's own AI translation plugin does this mainly here:
https://github.com/datocms/plugins/blob/master/ai-translations/src/utils/schemaRepository.ts

What do you think of this? Perhaps you'd rather use their plugin, I'm curious if you prefer our plugin for a specific reason.