From 6a07018016bc564d826653d97e9b1381095768e7 Mon Sep 17 00:00:00 2001 From: WofWca Date: Mon, 17 Mar 2025 22:27:57 +0400 Subject: [PATCH] mention that events use commands internally This is important to mention to make it clear to the developer what they need to do to secure their application. --- .../docs/concept/Inter-Process Communication/index.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/content/docs/concept/Inter-Process Communication/index.mdx b/src/content/docs/concept/Inter-Process Communication/index.mdx index 3117111cdf..79431fa78b 100644 --- a/src/content/docs/concept/Inter-Process Communication/index.mdx +++ b/src/content/docs/concept/Inter-Process Communication/index.mdx @@ -54,6 +54,12 @@ Core -> Frontend: "Event"{style.animated: true}
Events sent between the Core and the Webview.
+{/* This is important to mention to make it clear to the developer +what they need to do to secure their application. */} +Under the hood, events still utilize Commands, +and the access to the events API is controlled by the +[Event permissions](/reference/acl/core-permissions/#event). + ## Commands Tauri also provides a [foreign function interface]-like abstraction on top of IPC messages[^1]. The primary API, `invoke`, is similar to the browser's `fetch` API and allows the Frontend to invoke Rust functions, pass arguments, and receive data.