inkbridge 0.1.0-beta.18 → 0.1.0-beta.19

package/README.md

@@ -180,13 +180,13 @@ ignores:
     "react/forbid-dom-props": ["error", {
       "forbid": [{
         "propName": "style",
-        "message": "Inkbridge ignores inline styles — use Tailwind classes (or arbitrary values like text-[#0a0]) so Figma rendering matches the browser."
+        "message": "Use Tailwind classes — Inkbridge ignores inline styles."
       }]
     }],
     "react/forbid-component-props": ["error", {
       "forbid": [{
         "propName": "style",
-        "message": "Inkbridge ignores inline styles — use Tailwind classes (or arbitrary values like text-[#0a0]) so Figma rendering matches the browser."
+        "message": "Use Tailwind classes — Inkbridge ignores inline styles."
       }]
     }]
   }
@@ -261,15 +261,16 @@ Component data is always scanned live — you only need to update when a new `in
 
 ```
 Figma plugin (sandboxed)
-    └── code.js            Main logic — cannot make network requests directly
-    └── ui.html            Hidden iframe — relays all network requests to code.js
+    └── code.js     Main logic — no direct network access
+    └── ui.html     Hidden iframe — relays I/O for code.js
 
-code.js  →  ui.html  →  localhost:4000/api/inkbridge/scan-components
-                     →  localhost:4000/api/inkbridge/patch-tokens
-                     →  https://api.github.com
+code.js → ui.html → localhost:4000/api/inkbridge/scan-components
+                  → localhost:4000/api/inkbridge/patch-tokens
+                  → https://api.github.com
 ```
 
-All network I/O is relayed through the UI iframe via `postMessage` due to the Figma sandbox restriction.
+All network I/O is relayed through the UI iframe via `postMessage`
+because the Figma plugin sandbox can't make requests directly.
 
 ---