useblocks 1.1.85-dev.6 → 1.1.85-dev.7

package/README.md

@@ -150,9 +150,13 @@ const editor = emailmaker.create({
 await editor.ready;
 ```
 
-You can store the handle, subscribe to events or call `destroy()` right away. Before `ready`:
+You can store the handle, subscribe to events or call `destroy()` right away.
 
-| what | before ready |
+The handle is bound to the editor as soon as the editor is assembled — before the email from `content`
+is shown — so calls made from handlers (like `compileEmail()` above) reach the editor. Once bound,
+every call goes straight to the editor. Before binding:
+
+| what | before binding |
 | --- | --- |
 | `handle*` subscriptions | kept and attached before the first event — nothing is lost |
 | async methods (`show`, `compileEmail`, `getEmailSnapshot`, …) | wait for `ready`, then run |
@@ -166,6 +170,13 @@ After `destroy()` the handle is detached: its subscriptions are removed and its
 destroyed editor's. If another owner has already reused the element, destroying the previous handle
 leaves the editor alone and only takes its own subscriptions with it.
 
+Between binding and `ready` the email may not be shown yet. If you need the shown document — a
+`getEmailSnapshot()`, for example — await `ready` first.
+
+A second `create()` or `init()` into the same element while the first one is still starting waits for
+it and reuses its editor with the new options: both calls succeed and the editor belongs to the latest
+one.
+
 An initialisation error arrives as a `ready` rejection. If you create a handle and never await
 `ready`, such an error surfaces in the console as unhandled — on purpose, otherwise there is no way to
 learn the editor did not start. The exception is `destroy()` before `ready`: that rejection is
@@ -501,6 +512,7 @@ See typings (**`ExportedApi.DataMixin.Events`**) — includes for example **`han
 | handleSaveEmail           | Persist email (**`SaveEventPayload`**) |
 | handleReadEmailRevisions | Autosaves / revisions                |
 | handleEmailAutosave       | Autosave created                     |
+| handleEmailInit           | The email is shown on the canvas. Fires on every fill of the canvas with new content — at start and on each `show()` with another email; repeating the same show or reloading the canvas does not fire it. Do not build one-off actions ("save on first open") on it. |
 | handleReadBlocks          | Project blocks                       |
 | handleReadCommonBlocks    | Shared / common blocks               |
 | handleReadTemplateBlocks  | Template blocks for current email    |

package/iframe/.vite/manifest.json

@@ -11,8 +11,8 @@
     "src": "../packages/html2amp/rules.json",
     "isDynamicEntry": true
   },
-  "_discussHandlers.Ced_gtP0.js": {
-    "file": "js/discussHandlers.Ced_gtP0.js",
+  "_discussHandlers.C5qc-xPl.js": {
+    "file": "js/discussHandlers.C5qc-xPl.js",
     "name": "discussHandlers",
     "imports": [
       "_rolldown-runtime.BRlIiq3h.js"
@@ -39,7 +39,7 @@
     "src": "iframe-eblock.html",
     "isEntry": true,
     "imports": [
-      "_discussHandlers.Ced_gtP0.js",
+      "_discussHandlers.C5qc-xPl.js",
       "_typograf.all.BbXdyfMT.js"
     ]
   },
@@ -50,7 +50,7 @@
     "isEntry": true,
     "imports": [
       "_rolldown-runtime.BRlIiq3h.js",
-      "_discussHandlers.Ced_gtP0.js"
+      "_discussHandlers.C5qc-xPl.js"
     ],
     "dynamicImports": [
       "_typograf.all.BbXdyfMT.js"