fix: update field ID type and improve field handling

[caio-pizzol]

This commit modifies the TemplateField interface to allow the ID to be either a string or a number. It also updates the SuperDocTemplateBuilder component to handle the new ID type, ensuring that field insertion, deletion, and selection functions correctly accommodate both types. This change enhances flexibility in managing template fields.

[linear]

SD-548 Use numeric IDs for fields (XML/Word compatibility)

Summary

Remove ID generation from template-builder and let SuperDoc library handle it automatically using its proper generateRandomSigned32BitIntStrId() function

Tasks

• Remove const fieldId = \field_${Date.now()}`line frominsertFieldInternal`
• Remove id: fieldId from attrs passed to insertStructuredContentInline
• Remove id: fieldId from attrs passed to insertStructuredContentBlock
• Update TemplateField interface - keep id as string | number since SuperDoc returns it
• Test that fields are created with proper numeric IDs and work in Microsoft Word

Notes

Current problem (src/index.tsx):

const fieldId = `field_${Date.now()}`; // ❌ Template builder generates string ID

editor.commands.insertStructuredContentInline?.({
  attrs: {
    id: fieldId, // ❌ Passes ID to SuperDoc, bypassing auto-generation
    alias: field.alias,

SuperDoc already handles this (structured-content-commands.js):

const attrs = {
  ...options.attrs,
  id: options.attrs?.id || generateRandomSigned32BitIntStrId(), // ✅ Auto-generates if not provided
  tag: 'inline_text_sdt',
  alias: options.attrs?.alias || 'Structured content',
};

The fix - just delete the ID code:

// DELETE: const fieldId = `field_${Date.now()}`;

editor.commands.insertStructuredContentInline?.({
  attrs: {
    // DELETE: id: fieldId,
    alias: field.alias,
    tag: field.category,
  },
  text: field.defaultValue || field.alias,
});

Why this is better:

• SuperDoc knows the correct ID format (generateRandomSigned32BitIntStrId returns proper signed 32-bit int)
• Template builder doesn't need to know about ID generation
• Simpler code - fewer responsibilities
• IDs are guaranteed to be Word-compatible

After the fix: SuperDoc will automatically generate proper numeric IDs for all new fields

Testing: Create fields → export to .docx → open in Microsoft Word → verify SDT tags work correctly

[superdoc-bot]

🎉 This PR is included in version 0.2.0-next.3 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[superdoc-bot]

🎉 This PR is included in version 0.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀