Skip to content

mention that events use commands internally #3209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: v2
Choose a base branch
from
Open

mention that events use commands internally #3209

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/content/docs/concept/Inter-Process Communication/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,12 @@ Core -> Frontend: "Event"{style.animated: true}
<figcaption>Events sent between the Core and the Webview.</figcaption>
</figure>

{/* 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.
Expand Down