@magicx-eng/ai-autocomplete-angular 0.5.7 → 0.5.8

package/fesm2020/magicx-eng-ai-autocomplete-angular.mjs

@@ -579,16 +579,21 @@ class AIAutocompleteController {
         // handed. The core notifies listeners synchronously, and some actions
         // trigger reentrant `store.set` calls (e.g. typing a non-matching char
         // during re-edit makes the core synchronously exit re-edit and kick off a
-        // fetch). Reentrancy makes the outer set's listener loop continue with a
-        // now-stale snapshot, so the listener can fire *out of order* — delivering
-        // an older state (still in re-edit) after a newer one (re-edit exited).
-        // Reading `getState()` at emission time collapses every notification onto
-        // the true latest state, so a stale `editingParam` can't resurrect and
-        // retrigger the editor's re-edit caret-park (which would yank the caret
-        // back to where re-editing started). distinctUntilChanged downstream drops
-        // the resulting duplicate emissions. React avoids this because it batches
-        // renders and its caret effects are dependency-gated; our subscription is
-        // synchronous, so we coalesce here instead.
+        // fetch).
+        //
+        // The core's store used to deliver such a nested set inline and then
+        // resume the outer listener loop, so a listener could be handed an older
+        // state (still in re-edit) *after* a newer one (re-edit exited) — which
+        // resurrected a stale `editingParam` and retriggered the editor's re-edit
+        // caret-park, yanking the caret back to where re-editing started. The
+        // store now queues notifications and drains them in order, so that
+        // out-of-order delivery can no longer happen at the source.
+        //
+        // Reading `getState()` at emission time is kept as belt-and-braces: it
+        // costs nothing (distinctUntilChanged downstream drops the duplicate
+        // emissions) and keeps this bridge correct for any future consumer that
+        // emits mid-cascade. React needs neither, since it batches renders and
+        // gates its caret effects on dependencies.
         this.unsubscribeCore = this.core.subscribe(() => {
             if (!this.isDestroyed)
                 this.rawState$.next(this.core.getState());