chore(deps): update tauri monorepo (v2) (#1512)

* fix(deps): update tauri monorepo

* Create tauri-beta-23.md

* fix clippy - regen permissions

* revert accidental cargo.toml change

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Fabian-Lars <fabianlars@fabianlars.de>
This commit is contained in:
renovate[bot]
2024-07-02 11:23:48 +02:00
committed by GitHub
parent 955ed6aec6
commit 76daee7aaf
91 changed files with 7593 additions and 952 deletions
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,12 +1,140 @@
| Permission | Description |
|------|-----|
|`allow-init-auth`|Enables the init_auth command without any pre-configured scope.|
|`deny-init-auth`|Denies the init_auth command without any pre-configured scope.|
|`allow-register`|Enables the register command without any pre-configured scope.|
|`deny-register`|Denies the register command without any pre-configured scope.|
|`allow-sign`|Enables the sign command without any pre-configured scope.|
|`deny-sign`|Denies the sign command without any pre-configured scope.|
|`allow-verify-registration`|Enables the verify_registration command without any pre-configured scope.|
|`deny-verify-registration`|Denies the verify_registration command without any pre-configured scope.|
|`allow-verify-signature`|Enables the verify_signature command without any pre-configured scope.|
|`deny-verify-signature`|Denies the verify_signature command without any pre-configured scope.|
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`authenticator:allow-init-auth`
</td>
<td>
Enables the init_auth command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:deny-init-auth`
</td>
<td>
Denies the init_auth command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:allow-register`
</td>
<td>
Enables the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:deny-register`
</td>
<td>
Denies the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:allow-sign`
</td>
<td>
Enables the sign command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:deny-sign`
</td>
<td>
Denies the sign command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:allow-verify-registration`
</td>
<td>
Enables the verify_registration command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:deny-verify-registration`
</td>
<td>
Denies the verify_registration command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:allow-verify-signature`
</td>
<td>
Enables the verify_signature command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`authenticator:deny-verify-signature`
</td>
<td>
Denies the verify_signature command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
@@ -34,6 +34,7 @@ pub struct RegisteredKey {
#[serde(rename_all = "camelCase")]
pub struct RegisterResponse {
pub registration_data: String,
#[allow(unused)]
pub version: String,
pub client_data: String,
}
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,12 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-disable`|Enables the disable command without any pre-configured scope.|
|`deny-disable`|Denies the disable command without any pre-configured scope.|
|`allow-enable`|Enables the enable command without any pre-configured scope.|
|`deny-enable`|Denies the enable command without any pre-configured scope.|
|`allow-is-enabled`|Enables the is_enabled command without any pre-configured scope.|
|`deny-is-enabled`|Denies the is_enabled command without any pre-configured scope.|
|`default`|This permission set configures if your
## Default Permission
This permission set configures if your
application can enable or disable auto
starting the application on boot.
@@ -15,4 +9,96 @@ starting the application on boot.
It allows all to check, enable and
disable the automatic start on boot.
|
- `allow-enable`
- `allow-disable`
- `allow-is-enabled`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`autostart:allow-disable`
</td>
<td>
Enables the disable command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`autostart:deny-disable`
</td>
<td>
Denies the disable command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`autostart:allow-enable`
</td>
<td>
Enables the enable command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`autostart:deny-enable`
</td>
<td>
Denies the enable command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`autostart:allow-is-enabled`
</td>
<td>
Enables the is_enabled command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`autostart:deny-is-enabled`
</td>
<td>
Denies the is_enabled command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,22 +1,183 @@
| Permission | Description |
|------|-----|
|`allow-cancel`|Enables the cancel command without any pre-configured scope.|
|`deny-cancel`|Denies the cancel command without any pre-configured scope.|
|`allow-check-permissions`|Enables the check_permissions command without any pre-configured scope.|
|`deny-check-permissions`|Denies the check_permissions command without any pre-configured scope.|
|`allow-open-app-settings`|Enables the open_app_settings command without any pre-configured scope.|
|`deny-open-app-settings`|Denies the open_app_settings command without any pre-configured scope.|
|`allow-request-permissions`|Enables the request_permissions command without any pre-configured scope.|
|`deny-request-permissions`|Denies the request_permissions command without any pre-configured scope.|
|`allow-scan`|Enables the scan command without any pre-configured scope.|
|`deny-scan`|Denies the scan command without any pre-configured scope.|
|`allow-vibrate`|Enables the vibrate command without any pre-configured scope.|
|`deny-vibrate`|Denies the vibrate command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
barcode scanning features are by default exposed.
#### Granted Permissions
It allows all barcode related features.
|
- `allow-cancel`
- `allow-check-permissions`
- `allow-open-app-settings`
- `allow-request-permissions`
- `allow-scan`
- `allow-vibrate`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`barcode-scanner:allow-cancel`
</td>
<td>
Enables the cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-cancel`
</td>
<td>
Denies the cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:allow-check-permissions`
</td>
<td>
Enables the check_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-check-permissions`
</td>
<td>
Denies the check_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:allow-open-app-settings`
</td>
<td>
Enables the open_app_settings command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-open-app-settings`
</td>
<td>
Denies the open_app_settings command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:allow-request-permissions`
</td>
<td>
Enables the request_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-request-permissions`
</td>
<td>
Denies the request_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:allow-scan`
</td>
<td>
Enables the scan command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-scan`
</td>
<td>
Denies the scan command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:allow-vibrate`
</td>
<td>
Enables the vibrate command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`barcode-scanner:deny-vibrate`
</td>
<td>
Denies the vibrate command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,75 @@
| Permission | Description |
|------|-----|
|`allow-authenticate`|Enables the authenticate command without any pre-configured scope.|
|`deny-authenticate`|Denies the authenticate command without any pre-configured scope.|
|`allow-status`|Enables the status command without any pre-configured scope.|
|`deny-status`|Denies the status command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
biometric features are by default exposed.
#### Granted Permissions
It allows acccess to all biometric commands.
|
- `allow-authenticate`
- `allow-status`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`biometric:allow-authenticate`
</td>
<td>
Enables the authenticate command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`biometric:deny-authenticate`
</td>
<td>
Denies the authenticate command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`biometric:allow-status`
</td>
<td>
Enables the status command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`biometric:deny-status`
</td>
<td>
Denies the status command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,5 +1,41 @@
| Permission | Description |
|------|-----|
|`allow-cli-matches`|Enables the cli_matches command without any pre-configured scope.|
|`deny-cli-matches`|Denies the cli_matches command without any pre-configured scope.|
|`default`|Allows reading the CLI matches|
## Default Permission
Allows reading the CLI matches
- `allow-cli-matches`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`cli:allow-cli-matches`
</td>
<td>
Enables the cli_matches command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`cli:deny-cli-matches`
</td>
<td>
Denies the cli_matches command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,20 +1,175 @@
| Permission | Description |
|------|-----|
|`allow-clear`|Enables the clear command without any pre-configured scope.|
|`deny-clear`|Denies the clear command without any pre-configured scope.|
|`allow-read-image`|Enables the read_image command without any pre-configured scope.|
|`deny-read-image`|Denies the read_image command without any pre-configured scope.|
|`allow-read-text`|Enables the read_text command without any pre-configured scope.|
|`deny-read-text`|Denies the read_text command without any pre-configured scope.|
|`allow-write-html`|Enables the write_html command without any pre-configured scope.|
|`deny-write-html`|Denies the write_html command without any pre-configured scope.|
|`allow-write-image`|Enables the write_image command without any pre-configured scope.|
|`deny-write-image`|Denies the write_image command without any pre-configured scope.|
|`allow-write-text`|Enables the write_text command without any pre-configured scope.|
|`deny-write-text`|Denies the write_text command without any pre-configured scope.|
|`default`|No features are enabled by default, as we believe
## Default Permission
No features are enabled by default, as we believe
the clipboard can be inherently dangerous and it is
application specific if read and/or write access is needed.
Clipboard interaction needs to be explicitly enabled.
|
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`clipboard-manager:allow-clear`
</td>
<td>
Enables the clear command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-clear`
</td>
<td>
Denies the clear command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:allow-read-image`
</td>
<td>
Enables the read_image command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-read-image`
</td>
<td>
Denies the read_image command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:allow-read-text`
</td>
<td>
Enables the read_text command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-read-text`
</td>
<td>
Denies the read_text command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:allow-write-html`
</td>
<td>
Enables the write_html command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-write-html`
</td>
<td>
Denies the write_html command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:allow-write-image`
</td>
<td>
Enables the write_image command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-write-image`
</td>
<td>
Denies the write_image command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:allow-write-text`
</td>
<td>
Enables the write_text command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`clipboard-manager:deny-write-text`
</td>
<td>
Denies the write_text command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+2 -2
View File
@@ -10,11 +10,11 @@
"tauri": "tauri"
},
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13",
"@tauri-apps/api": "2.0.0-beta.14",
"@tauri-apps/plugin-deep-link": "2.0.0-beta.7"
},
"devDependencies": {
"@tauri-apps/cli": "2.0.0-beta.20",
"@tauri-apps/cli": "2.0.0-beta.21",
"internal-ip": "7.0.0",
"typescript": "^5.2.2",
"vite": "^5.0.13"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,11 +1,119 @@
| Permission | Description |
|------|-----|
|`allow-get-current`|Enables the get_current command without any pre-configured scope.|
|`deny-get-current`|Denies the get_current command without any pre-configured scope.|
|`allow-is-registered`|Enables the is_registered command without any pre-configured scope.|
|`deny-is-registered`|Denies the is_registered command without any pre-configured scope.|
|`allow-register`|Enables the register command without any pre-configured scope.|
|`deny-register`|Denies the register command without any pre-configured scope.|
|`allow-unregister`|Enables the unregister command without any pre-configured scope.|
|`deny-unregister`|Denies the unregister command without any pre-configured scope.|
|`default`|Allows reading the opened deep link via the get_current command|
## Default Permission
Allows reading the opened deep link via the get_current command
- `allow-get-current`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`deep-link:allow-get-current`
</td>
<td>
Enables the get_current command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:deny-get-current`
</td>
<td>
Denies the get_current command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:allow-is-registered`
</td>
<td>
Enables the is_registered command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:deny-is-registered`
</td>
<td>
Denies the is_registered command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:allow-register`
</td>
<td>
Enables the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:deny-register`
</td>
<td>
Denies the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:allow-unregister`
</td>
<td>
Enables the unregister command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`deep-link:deny-unregister`
</td>
<td>
Denies the unregister command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+2
View File
@@ -35,11 +35,13 @@ pub struct Config {
pub mobile: Vec<AssociatedDomain>,
/// Desktop requires urls starting with `<scheme>://`.
/// These urls are also active in dev mode on Android.
#[allow(unused)] // Used in tauri-bundler
pub desktop: DesktopProtocol,
}
#[derive(Deserialize)]
#[serde(untagged)]
#[allow(unused)] // Used in tauri-bundler
pub enum DesktopProtocol {
One(DeepLinkProtocol),
List(Vec<DeepLinkProtocol>),
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,16 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-ask`|Enables the ask command without any pre-configured scope.|
|`deny-ask`|Denies the ask command without any pre-configured scope.|
|`allow-confirm`|Enables the confirm command without any pre-configured scope.|
|`deny-confirm`|Denies the confirm command without any pre-configured scope.|
|`allow-message`|Enables the message command without any pre-configured scope.|
|`deny-message`|Denies the message command without any pre-configured scope.|
|`allow-open`|Enables the open command without any pre-configured scope.|
|`deny-open`|Denies the open command without any pre-configured scope.|
|`allow-save`|Enables the save command without any pre-configured scope.|
|`deny-save`|Denies the save command without any pre-configured scope.|
|`default`|This permission set configures the types of dialogs
## Default Permission
This permission set configures the types of dialogs
available from the dialog plugin.
#### Granted Permissions
@@ -18,4 +8,150 @@ available from the dialog plugin.
All dialog types are enabled.
|
- `allow-ask`
- `allow-confirm`
- `allow-message`
- `allow-save`
- `allow-open`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`dialog:allow-ask`
</td>
<td>
Enables the ask command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:deny-ask`
</td>
<td>
Denies the ask command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:allow-confirm`
</td>
<td>
Enables the confirm command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:deny-confirm`
</td>
<td>
Denies the confirm command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:allow-message`
</td>
<td>
Enables the message command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:deny-message`
</td>
<td>
Denies the message command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:allow-open`
</td>
<td>
Enables the open command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:deny-open`
</td>
<td>
Denies the open command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:allow-save`
</td>
<td>
Enables the save command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`dialog:deny-save`
</td>
<td>
Denies the save command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
File diff suppressed because it is too large Load Diff
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,17 +1,148 @@
| Permission | Description |
|------|-----|
|`allow-is-registered`|Enables the is_registered command without any pre-configured scope.|
|`deny-is-registered`|Denies the is_registered command without any pre-configured scope.|
|`allow-register`|Enables the register command without any pre-configured scope.|
|`deny-register`|Denies the register command without any pre-configured scope.|
|`allow-register-all`|Enables the register_all command without any pre-configured scope.|
|`deny-register-all`|Denies the register_all command without any pre-configured scope.|
|`allow-unregister`|Enables the unregister command without any pre-configured scope.|
|`deny-unregister`|Denies the unregister command without any pre-configured scope.|
|`allow-unregister-all`|Enables the unregister_all command without any pre-configured scope.|
|`deny-unregister-all`|Denies the unregister_all command without any pre-configured scope.|
|`default`|No features are enabled by default, as we believe
## Default Permission
No features are enabled by default, as we believe
the shortcuts can be inherently dangerous and it is
application specific if specific shortcuts should be
registered or unregistered.
|
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`global-shortcut:allow-is-registered`
</td>
<td>
Enables the is_registered command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:deny-is-registered`
</td>
<td>
Denies the is_registered command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:allow-register`
</td>
<td>
Enables the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:deny-register`
</td>
<td>
Denies the register command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:allow-register-all`
</td>
<td>
Enables the register_all command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:deny-register-all`
</td>
<td>
Denies the register_all command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:allow-unregister`
</td>
<td>
Enables the unregister command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:deny-unregister`
</td>
<td>
Denies the unregister command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:allow-unregister-all`
</td>
<td>
Enables the unregister_all command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`global-shortcut:deny-unregister-all`
</td>
<td>
Denies the unregister_all command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-fetch`|Enables the fetch command without any pre-configured scope.|
|`deny-fetch`|Denies the fetch command without any pre-configured scope.|
|`allow-fetch-cancel`|Enables the fetch_cancel command without any pre-configured scope.|
|`deny-fetch-cancel`|Denies the fetch_cancel command without any pre-configured scope.|
|`allow-fetch-read-body`|Enables the fetch_read_body command without any pre-configured scope.|
|`deny-fetch-read-body`|Denies the fetch_read_body command without any pre-configured scope.|
|`allow-fetch-send`|Enables the fetch_send command without any pre-configured scope.|
|`deny-fetch-send`|Denies the fetch_send command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
fetch operations are available from the http plugin.
This enables all fetch operations but does not
@@ -19,4 +11,123 @@ be manually configured before usage.
All fetch operations are enabled.
|
- `allow-fetch`
- `allow-fetch-cancel`
- `allow-fetch-read-body`
- `allow-fetch-send`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`http:allow-fetch`
</td>
<td>
Enables the fetch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:deny-fetch`
</td>
<td>
Denies the fetch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:allow-fetch-cancel`
</td>
<td>
Enables the fetch_cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:deny-fetch-cancel`
</td>
<td>
Denies the fetch_cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:allow-fetch-read-body`
</td>
<td>
Enables the fetch_read_body command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:deny-fetch-read-body`
</td>
<td>
Denies the fetch_read_body command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:allow-fetch-send`
</td>
<td>
Enables the fetch_send command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`http:deny-fetch-send`
</td>
<td>
Denies the fetch_send command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,5 +1,41 @@
| Permission | Description |
|------|-----|
|`allow-log`|Enables the log command without any pre-configured scope.|
|`deny-log`|Denies the log command without any pre-configured scope.|
|`default`|Allows the log command|
## Default Permission
Allows the log command
- `allow-log`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`log:allow-log`
</td>
<td>
Enables the log command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`log:deny-log`
</td>
<td>
Denies the log command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,12 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-is-available`|Enables the is_available command without any pre-configured scope.|
|`deny-is-available`|Denies the is_available command without any pre-configured scope.|
|`allow-scan`|Enables the scan command without any pre-configured scope.|
|`deny-scan`|Denies the scan command without any pre-configured scope.|
|`allow-write`|Enables the write command without any pre-configured scope.|
|`deny-write`|Denies the write command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
operations are available from the nfc plugin.
#### Granted Permissions
@@ -15,4 +9,95 @@ Checking if the NFC functionality is available
and scanning nearby tags is allowed.
Writing to tags needs to be manually enabled.
|
- `allow-is-available`
- `allow-scan`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`nfc:allow-is-available`
</td>
<td>
Enables the is_available command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`nfc:deny-is-available`
</td>
<td>
Denies the is_available command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`nfc:allow-scan`
</td>
<td>
Enables the scan command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`nfc:deny-scan`
</td>
<td>
Denies the scan command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`nfc:allow-write`
</td>
<td>
Enables the write command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`nfc:deny-write`
</td>
<td>
Denies the write command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,42 +1,453 @@
| Permission | Description |
|------|-----|
|`allow-batch`|Enables the batch command without any pre-configured scope.|
|`deny-batch`|Denies the batch command without any pre-configured scope.|
|`allow-cancel`|Enables the cancel command without any pre-configured scope.|
|`deny-cancel`|Denies the cancel command without any pre-configured scope.|
|`allow-check-permissions`|Enables the check_permissions command without any pre-configured scope.|
|`deny-check-permissions`|Denies the check_permissions command without any pre-configured scope.|
|`allow-create-channel`|Enables the create_channel command without any pre-configured scope.|
|`deny-create-channel`|Denies the create_channel command without any pre-configured scope.|
|`allow-delete-channel`|Enables the delete_channel command without any pre-configured scope.|
|`deny-delete-channel`|Denies the delete_channel command without any pre-configured scope.|
|`allow-get-active`|Enables the get_active command without any pre-configured scope.|
|`deny-get-active`|Denies the get_active command without any pre-configured scope.|
|`allow-get-pending`|Enables the get_pending command without any pre-configured scope.|
|`deny-get-pending`|Denies the get_pending command without any pre-configured scope.|
|`allow-is-permission-granted`|Enables the is_permission_granted command without any pre-configured scope.|
|`deny-is-permission-granted`|Denies the is_permission_granted command without any pre-configured scope.|
|`allow-list-channels`|Enables the list_channels command without any pre-configured scope.|
|`deny-list-channels`|Denies the list_channels command without any pre-configured scope.|
|`allow-notify`|Enables the notify command without any pre-configured scope.|
|`deny-notify`|Denies the notify command without any pre-configured scope.|
|`allow-permission-state`|Enables the permission_state command without any pre-configured scope.|
|`deny-permission-state`|Denies the permission_state command without any pre-configured scope.|
|`allow-register-action-types`|Enables the register_action_types command without any pre-configured scope.|
|`deny-register-action-types`|Denies the register_action_types command without any pre-configured scope.|
|`allow-register-listener`|Enables the register_listener command without any pre-configured scope.|
|`deny-register-listener`|Denies the register_listener command without any pre-configured scope.|
|`allow-remove-active`|Enables the remove_active command without any pre-configured scope.|
|`deny-remove-active`|Denies the remove_active command without any pre-configured scope.|
|`allow-request-permission`|Enables the request_permission command without any pre-configured scope.|
|`deny-request-permission`|Denies the request_permission command without any pre-configured scope.|
|`allow-show`|Enables the show command without any pre-configured scope.|
|`deny-show`|Denies the show command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
notification features are by default exposed.
#### Granted Permissions
It allows all notification related features.
|
- `allow-is-permission-granted`
- `allow-request-permission`
- `allow-notify`
- `allow-register-action-types`
- `allow-register-listener`
- `allow-cancel`
- `allow-get-pending`
- `allow-remove-active`
- `allow-get-active`
- `allow-check-permissions`
- `allow-show`
- `allow-batch`
- `allow-list-channels`
- `allow-delete-channel`
- `allow-create-channel`
- `allow-permission-state`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`notification:allow-batch`
</td>
<td>
Enables the batch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-batch`
</td>
<td>
Denies the batch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-cancel`
</td>
<td>
Enables the cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-cancel`
</td>
<td>
Denies the cancel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-check-permissions`
</td>
<td>
Enables the check_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-check-permissions`
</td>
<td>
Denies the check_permissions command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-create-channel`
</td>
<td>
Enables the create_channel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-create-channel`
</td>
<td>
Denies the create_channel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-delete-channel`
</td>
<td>
Enables the delete_channel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-delete-channel`
</td>
<td>
Denies the delete_channel command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-get-active`
</td>
<td>
Enables the get_active command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-get-active`
</td>
<td>
Denies the get_active command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-get-pending`
</td>
<td>
Enables the get_pending command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-get-pending`
</td>
<td>
Denies the get_pending command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-is-permission-granted`
</td>
<td>
Enables the is_permission_granted command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-is-permission-granted`
</td>
<td>
Denies the is_permission_granted command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-list-channels`
</td>
<td>
Enables the list_channels command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-list-channels`
</td>
<td>
Denies the list_channels command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-notify`
</td>
<td>
Enables the notify command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-notify`
</td>
<td>
Denies the notify command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-permission-state`
</td>
<td>
Enables the permission_state command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-permission-state`
</td>
<td>
Denies the permission_state command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-register-action-types`
</td>
<td>
Enables the register_action_types command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-register-action-types`
</td>
<td>
Denies the register_action_types command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-register-listener`
</td>
<td>
Enables the register_listener command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-register-listener`
</td>
<td>
Denies the register_listener command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-remove-active`
</td>
<td>
Enables the remove_active command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-remove-active`
</td>
<td>
Denies the remove_active command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-request-permission`
</td>
<td>
Enables the request_permission command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-request-permission`
</td>
<td>
Denies the request_permission command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:allow-show`
</td>
<td>
Enables the show command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`notification:deny-show`
</td>
<td>
Denies the show command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
+230 -20
View File
@@ -1,22 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-arch`|Enables the arch command without any pre-configured scope.|
|`deny-arch`|Denies the arch command without any pre-configured scope.|
|`allow-exe-extension`|Enables the exe_extension command without any pre-configured scope.|
|`deny-exe-extension`|Denies the exe_extension command without any pre-configured scope.|
|`allow-family`|Enables the family command without any pre-configured scope.|
|`deny-family`|Denies the family command without any pre-configured scope.|
|`allow-hostname`|Enables the hostname command without any pre-configured scope.|
|`deny-hostname`|Denies the hostname command without any pre-configured scope.|
|`allow-locale`|Enables the locale command without any pre-configured scope.|
|`deny-locale`|Denies the locale command without any pre-configured scope.|
|`allow-os-type`|Enables the os_type command without any pre-configured scope.|
|`deny-os-type`|Denies the os_type command without any pre-configured scope.|
|`allow-platform`|Enables the platform command without any pre-configured scope.|
|`deny-platform`|Denies the platform command without any pre-configured scope.|
|`allow-version`|Enables the version command without any pre-configured scope.|
|`deny-version`|Denies the version command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
operating system information are available
to gather from the frontend.
@@ -24,4 +8,230 @@ to gather from the frontend.
All information except the host name are available.
|
- `allow-arch`
- `allow-exe-extension`
- `allow-family`
- `allow-locale`
- `allow-os-type`
- `allow-platform`
- `allow-version`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`os:allow-arch`
</td>
<td>
Enables the arch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-arch`
</td>
<td>
Denies the arch command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-exe-extension`
</td>
<td>
Enables the exe_extension command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-exe-extension`
</td>
<td>
Denies the exe_extension command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-family`
</td>
<td>
Enables the family command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-family`
</td>
<td>
Denies the family command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-hostname`
</td>
<td>
Enables the hostname command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-hostname`
</td>
<td>
Denies the hostname command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-locale`
</td>
<td>
Enables the locale command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-locale`
</td>
<td>
Denies the locale command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-os-type`
</td>
<td>
Enables the os_type command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-os-type`
</td>
<td>
Denies the os_type command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-platform`
</td>
<td>
Enables the platform command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-platform`
</td>
<td>
Denies the platform command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:allow-version`
</td>
<td>
Enables the version command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`os:deny-version`
</td>
<td>
Denies the version command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,5 +1,41 @@
| Permission | Description |
|------|-----|
|`allow-move-window`|Enables the move_window command without any pre-configured scope.|
|`deny-move-window`|Denies the move_window command without any pre-configured scope.|
|`default`|Allows the move_window command|
## Default Permission
Allows the move_window command
- `allow-move-window`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`positioner:allow-move-window`
</td>
<td>
Enables the move_window command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`positioner:deny-move-window`
</td>
<td>
Denies the move_window command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,75 @@
| Permission | Description |
|------|-----|
|`allow-exit`|Enables the exit command without any pre-configured scope.|
|`deny-exit`|Denies the exit command without any pre-configured scope.|
|`allow-restart`|Enables the restart command without any pre-configured scope.|
|`deny-restart`|Denies the restart command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
process feeatures are by default exposed.
#### Granted Permissions
This enables to quit via `allow-exit` and restart via `allow-restart`
the application.
|
- `allow-exit`
- `allow-restart`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`process:allow-exit`
</td>
<td>
Enables the exit command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`process:deny-exit`
</td>
<td>
Denies the exit command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`process:allow-restart`
</td>
<td>
Enables the restart command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`process:deny-restart`
</td>
<td>
Denies the restart command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,16 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-execute`|Enables the execute command without any pre-configured scope.|
|`deny-execute`|Denies the execute command without any pre-configured scope.|
|`allow-kill`|Enables the kill command without any pre-configured scope.|
|`deny-kill`|Denies the kill command without any pre-configured scope.|
|`allow-open`|Enables the open command without any pre-configured scope.|
|`deny-open`|Denies the open command without any pre-configured scope.|
|`allow-spawn`|Enables the spawn command without any pre-configured scope.|
|`deny-spawn`|Denies the spawn command without any pre-configured scope.|
|`allow-stdin-write`|Enables the stdin_write command without any pre-configured scope.|
|`deny-stdin-write`|Denies the stdin_write command without any pre-configured scope.|
|`default`|This permission set configures which
## Default Permission
This permission set configures which
shell functionality is exposed by default.
#### Granted Permissions
@@ -18,4 +8,146 @@ shell functionality is exposed by default.
It allows to use the `open` functionality without any specific
scope pre-configured. It will allow opening `http(s)://`,
`tel:` and `mailto:` links.
|
- `allow-open`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`shell:allow-execute`
</td>
<td>
Enables the execute command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:deny-execute`
</td>
<td>
Denies the execute command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:allow-kill`
</td>
<td>
Enables the kill command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:deny-kill`
</td>
<td>
Denies the kill command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:allow-open`
</td>
<td>
Enables the open command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:deny-open`
</td>
<td>
Denies the open command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:allow-spawn`
</td>
<td>
Enables the spawn command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:deny-spawn`
</td>
<td>
Denies the spawn command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:allow-stdin-write`
</td>
<td>
Enables the stdin_write command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`shell:deny-stdin-write`
</td>
<td>
Denies the stdin_write command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+44 -44
View File
@@ -9,13 +9,13 @@
"version": "1.0.0",
"license": "MIT",
"devDependencies": {
"@tauri-apps/cli": "2.0.0-beta.20"
"@tauri-apps/cli": "2.0.0-beta.21"
}
},
"node_modules/@tauri-apps/cli": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli/-/cli-2.0.0-beta.20.tgz",
"integrity": "sha512-707q9uIc2oNrYHd2dtMvxTrpZXVpart5EIktnRymNOpphkLlB6WUBjHD+ga45WqTU6cNGKbYvkKqTNfshNul9Q==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli/-/cli-2.0.0-beta.21.tgz",
"integrity": "sha512-lqV4pD0iTs8ASd19slH0eRoVAjbxtD0cCsZFVD7kG4sYkeZ0IkvtxbvnHAOUbALfvnHZr1dVXFDVxQUqJK2OXw==",
"dev": true,
"license": "Apache-2.0 OR MIT",
"bin": {
@@ -29,22 +29,22 @@
"url": "https://opencollective.com/tauri"
},
"optionalDependencies": {
"@tauri-apps/cli-darwin-arm64": "2.0.0-beta.20",
"@tauri-apps/cli-darwin-x64": "2.0.0-beta.20",
"@tauri-apps/cli-linux-arm-gnueabihf": "2.0.0-beta.20",
"@tauri-apps/cli-linux-arm64-gnu": "2.0.0-beta.20",
"@tauri-apps/cli-linux-arm64-musl": "2.0.0-beta.20",
"@tauri-apps/cli-linux-x64-gnu": "2.0.0-beta.20",
"@tauri-apps/cli-linux-x64-musl": "2.0.0-beta.20",
"@tauri-apps/cli-win32-arm64-msvc": "2.0.0-beta.20",
"@tauri-apps/cli-win32-ia32-msvc": "2.0.0-beta.20",
"@tauri-apps/cli-win32-x64-msvc": "2.0.0-beta.20"
"@tauri-apps/cli-darwin-arm64": "2.0.0-beta.21",
"@tauri-apps/cli-darwin-x64": "2.0.0-beta.21",
"@tauri-apps/cli-linux-arm-gnueabihf": "2.0.0-beta.21",
"@tauri-apps/cli-linux-arm64-gnu": "2.0.0-beta.21",
"@tauri-apps/cli-linux-arm64-musl": "2.0.0-beta.21",
"@tauri-apps/cli-linux-x64-gnu": "2.0.0-beta.21",
"@tauri-apps/cli-linux-x64-musl": "2.0.0-beta.21",
"@tauri-apps/cli-win32-arm64-msvc": "2.0.0-beta.21",
"@tauri-apps/cli-win32-ia32-msvc": "2.0.0-beta.21",
"@tauri-apps/cli-win32-x64-msvc": "2.0.0-beta.21"
}
},
"node_modules/@tauri-apps/cli-darwin-arm64": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-darwin-arm64/-/cli-darwin-arm64-2.0.0-beta.20.tgz",
"integrity": "sha512-oCJOCib7GuYkwkBXx+ekamR8NZZU+2i3MLP+DHpDxK5gS2uhCE+CBkamJkNt6y1x6xdVnwyqZOm5RvN4SRtyIA==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-darwin-arm64/-/cli-darwin-arm64-2.0.0-beta.21.tgz",
"integrity": "sha512-okI7PRSC6RO4JfrOTqu4oWf0IfBPbkGHisyDOTay6K5uhz4zzry5fFJVa8S/DTrKtdjau4vcik/EDCxiGRun9Q==",
"cpu": [
"arm64"
],
@@ -59,9 +59,9 @@
}
},
"node_modules/@tauri-apps/cli-darwin-x64": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-darwin-x64/-/cli-darwin-x64-2.0.0-beta.20.tgz",
"integrity": "sha512-lC5QSnRExedYN4Ds6ZlSvC2PxP8qfIYBJQ5ktf+PJI5gQALdNeVtd6YnTG1ODCEklfLq9WKkGwp7JdALTU5wDA==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-darwin-x64/-/cli-darwin-x64-2.0.0-beta.21.tgz",
"integrity": "sha512-mXoJDXB6CBoqUnFb4TCsSVC6FJRZsN1DHRZAyn6iNLIhOrObcM4L2xz8rzt3WirANwJ/ayrNv95fEt8Fq1jmgA==",
"cpu": [
"x64"
],
@@ -76,9 +76,9 @@
}
},
"node_modules/@tauri-apps/cli-linux-arm-gnueabihf": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm-gnueabihf/-/cli-linux-arm-gnueabihf-2.0.0-beta.20.tgz",
"integrity": "sha512-nZCeBMHHye5DLOJV5k2w658hnCS+LYaOZ8y/G9l3ei+g0L/HBjlSy6r4simsAT5TG8+l3oCZzLBngfTMdDS/YA==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm-gnueabihf/-/cli-linux-arm-gnueabihf-2.0.0-beta.21.tgz",
"integrity": "sha512-LYPOx3LE2eZ0g8Zh/HYaNg6B1pZzH4BPMcma7wGZ0XPu+4fKLLGgav13xP2lknLnxiRP9jJCaTIBKXgcQEtLyg==",
"cpu": [
"arm"
],
@@ -93,9 +93,9 @@
}
},
"node_modules/@tauri-apps/cli-linux-arm64-gnu": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm64-gnu/-/cli-linux-arm64-gnu-2.0.0-beta.20.tgz",
"integrity": "sha512-B79ISVLPVBgwnCchVqwTKU+vxnFYqxKomcR4rmsvxfs0NVtT5QuNzE1k4NUQnw3966yjwhYR3mnHsSJQSB4Eyw==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm64-gnu/-/cli-linux-arm64-gnu-2.0.0-beta.21.tgz",
"integrity": "sha512-VP2L729tgY889OZj5U436EntjwkI8MyVB+GrvBv8k2mj1nWB651KiVIpcUmsUgjXZ2r01bifN9J0l+3EFEXUAQ==",
"cpu": [
"arm64"
],
@@ -110,9 +110,9 @@
}
},
"node_modules/@tauri-apps/cli-linux-arm64-musl": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm64-musl/-/cli-linux-arm64-musl-2.0.0-beta.20.tgz",
"integrity": "sha512-ojIkv/1uZHhcrgfIN8xgn4BBeo/Xg+bnV0wer6lD78zyxkUMWeEZ+u3mae1ejCJNhhaZOxNaUQ67MvDOiGyr5Q==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-arm64-musl/-/cli-linux-arm64-musl-2.0.0-beta.21.tgz",
"integrity": "sha512-s1rV01RIdowlPHfw7hTBnCEm2C3mZbynF+xpyRSv9vSczu4dpfwILMRwxB4nzMzdJ7RPHsf/R+5Ww86e8QM4Gw==",
"cpu": [
"arm64"
],
@@ -127,9 +127,9 @@
}
},
"node_modules/@tauri-apps/cli-linux-x64-gnu": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-x64-gnu/-/cli-linux-x64-gnu-2.0.0-beta.20.tgz",
"integrity": "sha512-xBy1FNbHKlc7T6pOmFQQPECxJaI5A9QWX7Kb9N64cNVusoOGlvc3xHYkXMS4PTr7xXOT0yiE1Ww2OwDRJ3lYsg==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-x64-gnu/-/cli-linux-x64-gnu-2.0.0-beta.21.tgz",
"integrity": "sha512-yGh7ktUycHT3mAnKxC7cx/vjcbjJzoxQCxnjWpmIayVwq+iXLD1mK7nRXRdJpL/rnBFTqqD29CKuypCEFiq3/A==",
"cpu": [
"x64"
],
@@ -144,9 +144,9 @@
}
},
"node_modules/@tauri-apps/cli-linux-x64-musl": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-x64-musl/-/cli-linux-x64-musl-2.0.0-beta.20.tgz",
"integrity": "sha512-+O6zq5jmtUxA1FUAAwF2ywPysy4NRo2Y6G+ESZDkY9XosRwdt5OUjqAsYktZA3AxDMZVei8r9buwTqUwi9ny/g==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-linux-x64-musl/-/cli-linux-x64-musl-2.0.0-beta.21.tgz",
"integrity": "sha512-+79b8O3tsjbGR47pJtcSKGmtqj4rsSxB5AfMb4UCkmoNkbaOzB0YS/ZieUGAb+SHXZ/MMs7mcl96N9SqYOL7hw==",
"cpu": [
"x64"
],
@@ -161,9 +161,9 @@
}
},
"node_modules/@tauri-apps/cli-win32-arm64-msvc": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-arm64-msvc/-/cli-win32-arm64-msvc-2.0.0-beta.20.tgz",
"integrity": "sha512-RswgMbWyOQcv53CHvIuiuhAh4kKDqaGyZfWD4VlxqX/XhkoF5gsNgr0MxzrY7pmoL+89oVI+fiGVJz4nOQE5vA==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-arm64-msvc/-/cli-win32-arm64-msvc-2.0.0-beta.21.tgz",
"integrity": "sha512-rKlpcjx6t1ECZciMmHT5xkXKjC+O+TVxRKmA21tEq/Ezt7XdnufGko1hduwQmVJWkHxKg6ab7uf98ImMpDC5UA==",
"cpu": [
"arm64"
],
@@ -178,9 +178,9 @@
}
},
"node_modules/@tauri-apps/cli-win32-ia32-msvc": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-ia32-msvc/-/cli-win32-ia32-msvc-2.0.0-beta.20.tgz",
"integrity": "sha512-5lgWmDVXhX3SBGbiv5SduM1yajiRnUEJClWhSdRrEEJeXdsxpCsBEhxYnUnDCEzPKxLLn5fdBv3VrVctJ03csQ==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-ia32-msvc/-/cli-win32-ia32-msvc-2.0.0-beta.21.tgz",
"integrity": "sha512-ExdhvRfgAoZi4/7re6OkmfqsHvTJQgWouTNphHWRilUEqBM7TEQV1UxYtwWfgyOKelyx4cxUYDFAJxootTb2Nw==",
"cpu": [
"ia32"
],
@@ -195,9 +195,9 @@
}
},
"node_modules/@tauri-apps/cli-win32-x64-msvc": {
"version": "2.0.0-beta.20",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-x64-msvc/-/cli-win32-x64-msvc-2.0.0-beta.20.tgz",
"integrity": "sha512-SuSiiVQTQPSzWlsxQp/NMzWbzDS9TdVDOw7CCfgiG5wnT2GsxzrcIAVN6i7ILsVFLxrjr0bIgPldSJcdcH84Yw==",
"version": "2.0.0-beta.21",
"resolved": "https://registry.npmjs.org/@tauri-apps/cli-win32-x64-msvc/-/cli-win32-x64-msvc-2.0.0-beta.21.tgz",
"integrity": "sha512-JtNTwNXIOfE04Cs3ieTvkdcMyJM9Sujw5MM9zNmusJKE03s/OLqbNK/2ISlcb/puwYGGPhhyYtL5hCmYXIrHHQ==",
"cpu": [
"x64"
],
@@ -9,6 +9,6 @@
"author": "",
"license": "MIT",
"devDependencies": {
"@tauri-apps/cli": "2.0.0-beta.20"
"@tauri-apps/cli": "2.0.0-beta.21"
}
}
@@ -2,8 +2,6 @@
// SPDX-License-Identifier: Apache-2.0
// SPDX-License-Identifier: MIT
#![cfg(target_os = "linux")]
#[cfg(feature = "semver")]
use crate::semver_compat::semver_compat_string;
@@ -2,8 +2,6 @@
// SPDX-License-Identifier: Apache-2.0
// SPDX-License-Identifier: MIT
#![cfg(target_os = "macos")]
use std::{
io::{BufWriter, Error, ErrorKind, Read, Write},
os::unix::net::{UnixListener, UnixStream},
@@ -2,8 +2,6 @@
// SPDX-License-Identifier: Apache-2.0
// SPDX-License-Identifier: MIT
#![cfg(target_os = "windows")]
#[cfg(feature = "semver")]
use crate::semver_compat::semver_compat_string;
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-close`|Enables the close command without any pre-configured scope.|
|`deny-close`|Denies the close command without any pre-configured scope.|
|`allow-execute`|Enables the execute command without any pre-configured scope.|
|`deny-execute`|Denies the execute command without any pre-configured scope.|
|`allow-load`|Enables the load command without any pre-configured scope.|
|`deny-load`|Denies the load command without any pre-configured scope.|
|`allow-select`|Enables the select command without any pre-configured scope.|
|`deny-select`|Denies the select command without any pre-configured scope.|
|`default`|# Tauri SQL Default Permissions
## Default Permission
# Tauri SQL Default Permissions
This permission set configures what kind of
database operations are available from the sql plugin.
@@ -18,4 +10,122 @@ database operations are available from the sql plugin.
All reading related operations are enabled.
Also allows to load or close a connection.
|
- `allow-close`
- `allow-load`
- `allow-select`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`sql:allow-close`
</td>
<td>
Enables the close command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:deny-close`
</td>
<td>
Denies the close command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:allow-execute`
</td>
<td>
Enables the execute command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:deny-execute`
</td>
<td>
Denies the execute command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:allow-load`
</td>
<td>
Enables the load command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:deny-load`
</td>
<td>
Denies the load command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:allow-select`
</td>
<td>
Enables the select command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`sql:deny-select`
</td>
<td>
Denies the select command without any pre-configured scope.
</td>
</tr>
</table>
+4 -4
View File
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,34 +1,345 @@
| Permission | Description |
|------|-----|
|`allow-clear`|Enables the clear command without any pre-configured scope.|
|`deny-clear`|Denies the clear command without any pre-configured scope.|
|`allow-delete`|Enables the delete command without any pre-configured scope.|
|`deny-delete`|Denies the delete command without any pre-configured scope.|
|`allow-entries`|Enables the entries command without any pre-configured scope.|
|`deny-entries`|Denies the entries command without any pre-configured scope.|
|`allow-get`|Enables the get command without any pre-configured scope.|
|`deny-get`|Denies the get command without any pre-configured scope.|
|`allow-has`|Enables the has command without any pre-configured scope.|
|`deny-has`|Denies the has command without any pre-configured scope.|
|`allow-keys`|Enables the keys command without any pre-configured scope.|
|`deny-keys`|Denies the keys command without any pre-configured scope.|
|`allow-length`|Enables the length command without any pre-configured scope.|
|`deny-length`|Denies the length command without any pre-configured scope.|
|`allow-load`|Enables the load command without any pre-configured scope.|
|`deny-load`|Denies the load command without any pre-configured scope.|
|`allow-reset`|Enables the reset command without any pre-configured scope.|
|`deny-reset`|Denies the reset command without any pre-configured scope.|
|`allow-save`|Enables the save command without any pre-configured scope.|
|`deny-save`|Denies the save command without any pre-configured scope.|
|`allow-set`|Enables the set command without any pre-configured scope.|
|`deny-set`|Denies the set command without any pre-configured scope.|
|`allow-values`|Enables the values command without any pre-configured scope.|
|`deny-values`|Denies the values command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
operations are available from the store plugin.
#### Granted Permissions
All operations are enabled by default.
|
- `allow-clear`
- `allow-delete`
- `allow-entries`
- `allow-get`
- `allow-has`
- `allow-keys`
- `allow-length`
- `allow-load`
- `allow-reset`
- `allow-save`
- `allow-set`
- `allow-values`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`store:allow-clear`
</td>
<td>
Enables the clear command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-clear`
</td>
<td>
Denies the clear command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-delete`
</td>
<td>
Enables the delete command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-delete`
</td>
<td>
Denies the delete command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-entries`
</td>
<td>
Enables the entries command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-entries`
</td>
<td>
Denies the entries command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-get`
</td>
<td>
Enables the get command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-get`
</td>
<td>
Denies the get command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-has`
</td>
<td>
Enables the has command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-has`
</td>
<td>
Denies the has command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-keys`
</td>
<td>
Enables the keys command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-keys`
</td>
<td>
Denies the keys command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-length`
</td>
<td>
Enables the length command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-length`
</td>
<td>
Denies the length command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-load`
</td>
<td>
Enables the load command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-load`
</td>
<td>
Denies the load command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-reset`
</td>
<td>
Enables the reset command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-reset`
</td>
<td>
Denies the reset command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-save`
</td>
<td>
Enables the save command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-save`
</td>
<td>
Denies the save command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-set`
</td>
<td>
Enables the set command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-set`
</td>
<td>
Denies the set command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:allow-values`
</td>
<td>
Enables the values command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`store:deny-values`
</td>
<td>
Denies the values command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,32 +1,315 @@
| Permission | Description |
|------|-----|
|`allow-create-client`|Enables the create_client command without any pre-configured scope.|
|`deny-create-client`|Denies the create_client command without any pre-configured scope.|
|`allow-destroy`|Enables the destroy command without any pre-configured scope.|
|`deny-destroy`|Denies the destroy command without any pre-configured scope.|
|`allow-execute-procedure`|Enables the execute_procedure command without any pre-configured scope.|
|`deny-execute-procedure`|Denies the execute_procedure command without any pre-configured scope.|
|`allow-get-store-record`|Enables the get_store_record command without any pre-configured scope.|
|`deny-get-store-record`|Denies the get_store_record command without any pre-configured scope.|
|`allow-initialize`|Enables the initialize command without any pre-configured scope.|
|`deny-initialize`|Denies the initialize command without any pre-configured scope.|
|`allow-load-client`|Enables the load_client command without any pre-configured scope.|
|`deny-load-client`|Denies the load_client command without any pre-configured scope.|
|`allow-remove-secret`|Enables the remove_secret command without any pre-configured scope.|
|`deny-remove-secret`|Denies the remove_secret command without any pre-configured scope.|
|`allow-remove-store-record`|Enables the remove_store_record command without any pre-configured scope.|
|`deny-remove-store-record`|Denies the remove_store_record command without any pre-configured scope.|
|`allow-save`|Enables the save command without any pre-configured scope.|
|`deny-save`|Denies the save command without any pre-configured scope.|
|`allow-save-secret`|Enables the save_secret command without any pre-configured scope.|
|`deny-save-secret`|Denies the save_secret command without any pre-configured scope.|
|`allow-save-store-record`|Enables the save_store_record command without any pre-configured scope.|
|`deny-save-store-record`|Denies the save_store_record command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
operations are available from the stronghold plugin.
#### Granted Permissions
All non-destructive operations are enabled by default.
|
- `allow-create-client`
- `allow-get-store-record`
- `allow-initialize`
- `allow-execute-procedure`
- `allow-load-client`
- `allow-save-secret`
- `allow-save-store-record`
- `allow-save`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`stronghold:allow-create-client`
</td>
<td>
Enables the create_client command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-create-client`
</td>
<td>
Denies the create_client command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-destroy`
</td>
<td>
Enables the destroy command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-destroy`
</td>
<td>
Denies the destroy command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-execute-procedure`
</td>
<td>
Enables the execute_procedure command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-execute-procedure`
</td>
<td>
Denies the execute_procedure command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-get-store-record`
</td>
<td>
Enables the get_store_record command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-get-store-record`
</td>
<td>
Denies the get_store_record command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-initialize`
</td>
<td>
Enables the initialize command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-initialize`
</td>
<td>
Denies the initialize command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-load-client`
</td>
<td>
Enables the load_client command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-load-client`
</td>
<td>
Denies the load_client command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-remove-secret`
</td>
<td>
Enables the remove_secret command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-remove-secret`
</td>
<td>
Denies the remove_secret command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-remove-store-record`
</td>
<td>
Enables the remove_store_record command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-remove-store-record`
</td>
<td>
Denies the remove_store_record command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-save`
</td>
<td>
Enables the save command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-save`
</td>
<td>
Denies the save command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-save-secret`
</td>
<td>
Enables the save_secret command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-save-secret`
</td>
<td>
Denies the save_secret command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:allow-save-store-record`
</td>
<td>
Enables the save_store_record command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`stronghold:deny-save-store-record`
</td>
<td>
Denies the save_store_record command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,6 @@
| Permission | Description |
|------|-----|
|`allow-check`|Enables the check command without any pre-configured scope.|
|`deny-check`|Denies the check command without any pre-configured scope.|
|`allow-download`|Enables the download command without any pre-configured scope.|
|`deny-download`|Denies the download command without any pre-configured scope.|
|`allow-download-and-install`|Enables the download_and_install command without any pre-configured scope.|
|`deny-download-and-install`|Denies the download_and_install command without any pre-configured scope.|
|`allow-install`|Enables the install command without any pre-configured scope.|
|`deny-install`|Denies the install command without any pre-configured scope.|
|`default`|This permission set configures which kind of
## Default Permission
This permission set configures which kind of
updater functions are exposed to the frontend.
#### Granted Permissions
@@ -16,4 +8,123 @@ updater functions are exposed to the frontend.
The full workflow from checking for updates to installing them
is enabled.
|
- `allow-check`
- `allow-download`
- `allow-install`
- `allow-download-and-install`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`updater:allow-check`
</td>
<td>
Enables the check command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:deny-check`
</td>
<td>
Denies the check command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:allow-download`
</td>
<td>
Enables the download command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:deny-download`
</td>
<td>
Denies the download command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:allow-download-and-install`
</td>
<td>
Enables the download_and_install command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:deny-download-and-install`
</td>
<td>
Denies the download_and_install command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:allow-install`
</td>
<td>
Enables the install command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`updater:deny-install`
</td>
<td>
Denies the install command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,14 +1,75 @@
| Permission | Description |
|------|-----|
|`allow-download`|Enables the download command without any pre-configured scope.|
|`deny-download`|Denies the download command without any pre-configured scope.|
|`allow-upload`|Enables the upload command without any pre-configured scope.|
|`deny-upload`|Denies the upload command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
operations are available from the upload plugin.
#### Granted Permissions
All operations are enabled by default.
|
- `allow-upload`
- `allow-download`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`upload:allow-download`
</td>
<td>
Enables the download command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`upload:deny-download`
</td>
<td>
Denies the download command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`upload:allow-upload`
</td>
<td>
Enables the upload command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`upload:deny-upload`
</td>
<td>
Denies the upload command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
@@ -9,7 +9,7 @@
"preview": "vite preview"
},
"devDependencies": {
"@tauri-apps/cli": "2.0.0-beta.20",
"@tauri-apps/cli": "2.0.0-beta.21",
"typescript": "^5.3.3",
"vite": "^5.0.13"
},
+1 -1
View File
@@ -23,6 +23,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,7 +1,68 @@
| Permission | Description |
|------|-----|
|`allow-connect`|Enables the connect command without any pre-configured scope.|
|`deny-connect`|Denies the connect command without any pre-configured scope.|
|`allow-send`|Enables the send command without any pre-configured scope.|
|`deny-send`|Denies the send command without any pre-configured scope.|
|`default`|Allows connecting and sending data to a WebSocket server|
## Default Permission
Allows connecting and sending data to a WebSocket server
- `allow-connect`
- `allow-send`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`websocket:allow-connect`
</td>
<td>
Enables the connect command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`websocket:deny-connect`
</td>
<td>
Denies the connect command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`websocket:allow-send`
</td>
<td>
Enables the send command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`websocket:deny-send`
</td>
<td>
Denies the send command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"
+1 -1
View File
@@ -24,6 +24,6 @@
"LICENSE"
],
"dependencies": {
"@tauri-apps/api": "2.0.0-beta.13"
"@tauri-apps/api": "2.0.0-beta.14"
}
}
@@ -1,16 +1,102 @@
| Permission | Description |
|------|-----|
|`allow-filename`|Enables the filename command without any pre-configured scope.|
|`deny-filename`|Denies the filename command without any pre-configured scope.|
|`allow-restore-state`|Enables the restore_state command without any pre-configured scope.|
|`deny-restore-state`|Denies the restore_state command without any pre-configured scope.|
|`allow-save-window-state`|Enables the save_window_state command without any pre-configured scope.|
|`deny-save-window-state`|Denies the save_window_state command without any pre-configured scope.|
|`default`|This permission set configures what kind of
## Default Permission
This permission set configures what kind of
operations are available from the window state plugin.
#### Granted Permissions
All operations are enabled by default.
|
- `allow-filename`
- `allow-restore-state`
- `allow-save-window-state`
### Permission Table
<table>
<tr>
<th>Identifier</th>
<th>Description</th>
</tr>
<tr>
<td>
`window-state:allow-filename`
</td>
<td>
Enables the filename command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`window-state:deny-filename`
</td>
<td>
Denies the filename command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`window-state:allow-restore-state`
</td>
<td>
Enables the restore_state command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`window-state:deny-restore-state`
</td>
<td>
Denies the restore_state command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`window-state:allow-save-window-state`
</td>
<td>
Enables the save_window_state command without any pre-configured scope.
</td>
</tr>
<tr>
<td>
`window-state:deny-save-window-state`
</td>
<td>
Denies the save_window_state command without any pre-configured scope.
</td>
</tr>
</table>
@@ -49,7 +49,7 @@
"minimum": 1.0
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -111,7 +111,7 @@
"type": "string"
},
"description": {
"description": "Human-readable description of what the permission does.",
"description": "Human-readable description of what the permission does. Tauri internal convention is to use <h4> headings in markdown content for Tauri documentation generation purposes.",
"type": [
"string",
"null"
@@ -172,7 +172,7 @@
}
},
"Scopes": {
"description": "A restriction of the command/endpoint functionality.\n\nIt can be of any serde serializable type and is used for allowing or preventing certain actions inside a Tauri command.\n\nThe scope is passed to the command and handled/enforced by the command itself.",
"description": "An argument for fine grained behavior control of Tauri commands.\n\nIt can be of any serde serializable type and is used to allow or prevent certain actions inside a Tauri command. The configured scope is passed to the command and will be enforced by the command implementation.\n\n## Example\n\n```json { \"allow\": [{ \"path\": \"$HOME/**\" }], \"deny\": [{ \"path\": \"$HOME/secret.txt\" }] } ```",
"type": "object",
"properties": {
"allow": {
@@ -186,7 +186,7 @@
}
},
"deny": {
"description": "Data that defines what is denied by the scope.",
"description": "Data that defines what is denied by the scope. This should be prioritized by validation logic.",
"type": [
"array",
"null"