glossary:entry-saved

`glossary:entry-saved`

Emitted after a glossary entry is successfully created or updated, notifying the editor and other components that glossary data has changed and content marks may need refreshing.

Schema

{
  module: 'glossary';
  type: 'entry-saved';
  payload: {
    id: string;  // UUID of the glossary entry that was saved
  }
}

Emitted By

Source	Condition
GlossaryEntryForm → handleSave()	After a successful `glossaryStore.createEntry()` call (create mode)
GlossaryEntryForm → handleSave()	After a successful `glossaryStore.updateEntry()` call (edit mode)

Dispatched via the convenience function dispatchGlossaryEntrySaved(entryId) from moduleEventBus.

Consumed By

Subscriber	Action Taken
TextEditor → onMount subscription	Calls `editor.clearGlossaryTooltipCache()` to invalidate cached tooltip data so the next hover fetches fresh definitions
Editor page (`+page.svelte`)	After a 3-second delay, reloads the currently selected content document to pick up any new `glossaryLink` marks applied by the background TermScanHandler
GlossaryEntryDetail → onMount subscription	After a 4-second delay, reloads the entry's usage/occurrence count to reflect marks applied by the background scan

Payload Fields

Field	Type	Description
`id`	`string`	The UUID of the glossary entry that was created or updated

Notes

The 3-second and 4-second delays in subscribers are heuristics to allow the backend TermScanHandler background job to complete before reloading. If the scan takes longer than expected, the editor may briefly show stale mark state. A subsequent manual content reload will pick up the final marks.

This event triggers the spellcheck dictionary integration indirectly: GlossaryEntryForm calls dictionaryStore.addWordIfMisspelled() for the term and all aliases after dispatching this event (with a 2-second delay).