feat: implement field filtering in FieldMenu with query support

[caio-pizzol]

Note

Adds live query filtering to the field menu driven by trigger typing and switches DOCX export to use the editor API.

• Editor/UX:
  • Add live query filtering for FieldMenu based on text typed after trigger in index.tsx (tracks trigger start, updates query, repositions menu, resets on close/select).
  • Improve trigger cleanup and position handling using triggerStart and current selection.
• FieldMenu:
  • Extend props with filteredFields and filterQuery; render header, filter status, and “No matching fields”; display filtered list when provided.
• Export:
  • Replace superdoc export with editor.exportDocx({ fileName }).
• Types:
  • Update FieldMenuProps to include filteredFields and filterQuery.
• Tests:
  • Remove src/__tests__/SuperDocTemplateBuilder.test.tsx and src/test/setup.ts.

^{Written by Cursor Bugbot for commit cb74d3a. This will update automatically on new commits. Configure here.}

[linear]

SD-529 Add Filtering to Field Menu on Double Curly Bracket Trigger

Summary

Enable field menu filtering as users type after the {{ trigger, showing only matching fields.

Tasks

• Detect when user types {{ to open the field menu
• Capture subsequent keystrokes after the trigger
• Filter availableFields array to show only fields matching the typed text
• Update field menu display in real-time as user continues typing
• Ensure field selection works with filtered results

Notes

The field menu component (src/defaults/FieldMenu.tsx) currently shows all available fields when triggered. We need to add state tracking for the search query and filter the displayed fields based on field label/category matching. The trigger detection logic exists in src/index.tsx where the editor's update event checks for {{ pattern.

[caio-pizzol]

cursor review

[cursor]

Bug: Trigger Cleanup Fails to Remove Query Text

The trigger cleanup function captures the cursor position at trigger detection, causing it to only delete the trigger characters when executed, leaving any typed filter query text in the document. Additionally, menuTriggerFromRef.current is set to the position after the trigger, which causes incorrect menu dismissal when the cursor moves before the trigger.

src/index.tsx#L259-L267

template-builder/src/index.tsx

Lines 259 to 267 in cb74d3a

	const cleanup = () => {
	const currentPos = e.state.selection.from;
	const tr = e.state.tr.delete(triggerStart, currentPos);
	e.view.dispatch(tr);
	};
	triggerCleanupRef.current = cleanup;
	menuTriggerFromRef.current = from;

 

---