artin/tauri
1
0
Fork 0
mirror of https://github.com/tauri-apps/tauri.git synced 2026-02-06 13:57:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: how security > capabilities works (#13946)

Browse Source 
* docs: how `security > capabilities` works

* Add how to use it

* Apply suggestions

* Relative to `Cargo.toml`

* Remove the relative base wording
This commit is contained in:
Tony 2025-08-04 18:13:02 +08:00 committed by GitHub
parent 4d270a96a8
commit 7d21e3b2fa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 22 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
crates/tauri-cli/config.schema.json
View File

@ -1150,7 +1150,7 @@
]
},
"capabilities": {
"description": "List of capabilities that are enabled on the application.\n\n If the list is empty, all capabilities are included.",
"description": "List of capabilities that are enabled on the application.\n\n By default (not set or empty list), all capability files from `./capabilities/` are included,\n by setting values in this entry, you have fine grained control over which capabilities are included\n\n You can either reference a capability file defined in `./capabilities/` with its identifier or inline a [`Capability`]\n\n ### Example\n\n ```json\n {\n \"app\": {\n \"capabilities\": [\n \"main-window\",\n {\n \"identifier\": \"drag-window\",\n \"permissions\": [\"core:window:allow-start-dragging\"]\n }\n ]\n }\n }\n ```",
"default": [],
"type": "array",
"items": {

2
crates/tauri-schema-generator/schemas/config.schema.json
View File

@ -1150,7 +1150,7 @@
]
},
"capabilities": {
"description": "List of capabilities that are enabled on the application.\n\n If the list is empty, all capabilities are included.",
"description": "List of capabilities that are enabled on the application.\n\n By default (not set or empty list), all capability files from `./capabilities/` are included,\n by setting values in this entry, you have fine grained control over which capabilities are included\n\n You can either reference a capability file defined in `./capabilities/` with its identifier or inline a [`Capability`]\n\n ### Example\n\n ```json\n {\n \"app\": {\n \"capabilities\": [\n \"main-window\",\n {\n \"identifier\": \"drag-window\",\n \"permissions\": [\"core:window:allow-start-dragging\"]\n }\n ]\n }\n }\n ```",
"default": [],
"type": "array",
"items": {

21
crates/tauri-utils/src/config.rs
View File

@ -2468,7 +2468,26 @@ pub struct SecurityConfig {
pub pattern: PatternKind,
/// List of capabilities that are enabled on the application.
///
/// If the list is empty, all capabilities are included.
/// By default (not set or empty list), all capability files from `./capabilities/` are included,
/// by setting values in this entry, you have fine grained control over which capabilities are included
///
/// You can either reference a capability file defined in `./capabilities/` with its identifier or inline a [`Capability`]
///
/// ### Example
///
/// ```json
/// {
/// "app": {
/// "capabilities": [
/// "main-window",
/// {
/// "identifier": "drag-window",
/// "permissions": ["core:window:allow-start-dragging"]
/// }
/// ]
/// }
/// }
/// ```
#[serde(default)]
pub capabilities: Vec<CapabilityEntry>,
/// The headers, which are added to every http response from tauri to the web view