You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: archived/lunar/src-tauri/gen/schemas/desktop-schema.json
+2-2
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@
37
37
],
38
38
"definitions": {
39
39
"Capability": {
40
-
"description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows fine grained access to the Tauri core, application, or plugin commands. If a window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, \"platforms\": [\"macOS\",\"windows\"] } ```",
40
+
"description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows fine grained access to the Tauri core, application, or plugin commands. If a window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, ], \"platforms\": [\"macOS\",\"windows\"] } ```",
41
41
"type": "object",
42
42
"required": [
43
43
"identifier",
@@ -84,7 +84,7 @@
84
84
}
85
85
},
86
86
"permissions": {
87
-
"description": "List of permissions attached to this capability.\n\nMust include the plugin name as prefix in the form of `${plugin-name}:${permission-name}`. For commands directly implemented in the application itself only `${permission-name}` is required.\n\n## Example\n\n```json [ \"core:default\", \"shell:allow-open\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] } ```",
87
+
"description": "List of permissions attached to this capability.\n\nMust include the plugin name as prefix in the form of `${plugin-name}:${permission-name}`. For commands directly implemented in the application itself only `${permission-name}` is required.\n\n## Example\n\n```json [ \"core:default\", \"shell:allow-open\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] } ] ```",
Copy file name to clipboardexpand all lines: archived/lunar/src-tauri/gen/schemas/macOS-schema.json
+46-46
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@
37
37
],
38
38
"definitions": {
39
39
"Capability": {
40
-
"description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows fine grained access to the Tauri core, application, or plugin commands. If a window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, \"platforms\": [\"macOS\",\"windows\"] } ```",
40
+
"description": "A grouping and boundary mechanism developers can use to isolate access to the IPC layer.\n\nIt controls application windows fine grained access to the Tauri core, application, or plugin commands. If a window is not matching any capability then it has no access to the IPC layer at all.\n\nThis can be done to create groups of windows, based on their required system access, which can reduce impact of frontend vulnerabilities in less privileged windows. Windows can be added to a capability by exact name (e.g. `main-window`) or glob patterns like `*` or `admin-*`. A Window can have none, one, or multiple associated capabilities.\n\n## Example\n\n```json { \"identifier\": \"main-user-files-write\", \"description\": \"This capability allows the `main` window on macOS and Windows access to `filesystem` write related commands and `dialog` commands to enable programatic access to files selected by the user.\", \"windows\": [ \"main\" ], \"permissions\": [ \"core:default\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] }, ], \"platforms\": [\"macOS\",\"windows\"] } ```",
41
41
"type": "object",
42
42
"required": [
43
43
"identifier",
@@ -84,7 +84,7 @@
84
84
}
85
85
},
86
86
"permissions": {
87
-
"description": "List of permissions attached to this capability.\n\nMust include the plugin name as prefix in the form of `${plugin-name}:${permission-name}`. For commands directly implemented in the application itself only `${permission-name}` is required.\n\n## Example\n\n```json [ \"core:default\", \"shell:allow-open\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] } ```",
87
+
"description": "List of permissions attached to this capability.\n\nMust include the plugin name as prefix in the form of `${plugin-name}:${permission-name}`. For commands directly implemented in the application itself only `${permission-name}` is required.\n\n## Example\n\n```json [ \"core:default\", \"shell:allow-open\", \"dialog:open\", { \"identifier\": \"fs:allow-write-text-file\", \"allow\": [{ \"path\": \"$HOME/test.txt\" }] } ] ```",
88
88
"type": "array",
89
89
"items": {
90
90
"$ref": "#/definitions/PermissionEntry"
@@ -1714,21 +1714,21 @@
1714
1714
"name"
1715
1715
],
1716
1716
"properties": {
1717
+
"name": {
1718
+
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1719
+
"type": "string"
1720
+
},
1721
+
"cmd": {
1722
+
"description": "The command name. It can start with a variable that resolves to a system base directory. The variables are: `$AUDIO`, `$CACHE`, `$CONFIG`, `$DATA`, `$LOCALDATA`, `$DESKTOP`, `$DOCUMENT`, `$DOWNLOAD`, `$EXE`, `$FONT`, `$HOME`, `$PICTURE`, `$PUBLIC`, `$RUNTIME`, `$TEMPLATE`, `$VIDEO`, `$RESOURCE`, `$LOG`, `$TEMP`, `$APPCONFIG`, `$APPDATA`, `$APPLOCALDATA`, `$APPCACHE`, `$APPLOG`.",
1723
+
"type": "string"
1724
+
},
1717
1725
"args": {
1718
1726
"description": "The allowed arguments for the command execution.",
"description": "The command name. It can start with a variable that resolves to a system base directory. The variables are: `$AUDIO`, `$CACHE`, `$CONFIG`, `$DATA`, `$LOCALDATA`, `$DESKTOP`, `$DOCUMENT`, `$DOWNLOAD`, `$EXE`, `$FONT`, `$HOME`, `$PICTURE`, `$PUBLIC`, `$RUNTIME`, `$TEMPLATE`, `$VIDEO`, `$RESOURCE`, `$LOG`, `$TEMP`, `$APPCONFIG`, `$APPDATA`, `$APPLOCALDATA`, `$APPCACHE`, `$APPLOG`.",
1727
-
"type": "string"
1728
-
},
1729
-
"name": {
1730
-
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1731
-
"type": "string"
1732
1732
}
1733
1733
},
1734
1734
"additionalProperties": false
@@ -1740,6 +1740,10 @@
1740
1740
"sidecar"
1741
1741
],
1742
1742
"properties": {
1743
+
"name": {
1744
+
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1745
+
"type": "string"
1746
+
},
1743
1747
"args": {
1744
1748
"description": "The allowed arguments for the command execution.",
1745
1749
"allOf": [
@@ -1748,10 +1752,6 @@
1748
1752
}
1749
1753
]
1750
1754
},
1751
-
"name": {
1752
-
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1753
-
"type": "string"
1754
-
},
1755
1755
"sidecar": {
1756
1756
"description": "If this command is a sidecar command.",
1757
1757
"type": "boolean"
@@ -1774,21 +1774,21 @@
1774
1774
"name"
1775
1775
],
1776
1776
"properties": {
1777
+
"name": {
1778
+
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1779
+
"type": "string"
1780
+
},
1781
+
"cmd": {
1782
+
"description": "The command name. It can start with a variable that resolves to a system base directory. The variables are: `$AUDIO`, `$CACHE`, `$CONFIG`, `$DATA`, `$LOCALDATA`, `$DESKTOP`, `$DOCUMENT`, `$DOWNLOAD`, `$EXE`, `$FONT`, `$HOME`, `$PICTURE`, `$PUBLIC`, `$RUNTIME`, `$TEMPLATE`, `$VIDEO`, `$RESOURCE`, `$LOG`, `$TEMP`, `$APPCONFIG`, `$APPDATA`, `$APPLOCALDATA`, `$APPCACHE`, `$APPLOG`.",
1783
+
"type": "string"
1784
+
},
1777
1785
"args": {
1778
1786
"description": "The allowed arguments for the command execution.",
"description": "The command name. It can start with a variable that resolves to a system base directory. The variables are: `$AUDIO`, `$CACHE`, `$CONFIG`, `$DATA`, `$LOCALDATA`, `$DESKTOP`, `$DOCUMENT`, `$DOWNLOAD`, `$EXE`, `$FONT`, `$HOME`, `$PICTURE`, `$PUBLIC`, `$RUNTIME`, `$TEMPLATE`, `$VIDEO`, `$RESOURCE`, `$LOG`, `$TEMP`, `$APPCONFIG`, `$APPDATA`, `$APPLOCALDATA`, `$APPCACHE`, `$APPLOG`.",
1787
-
"type": "string"
1788
-
},
1789
-
"name": {
1790
-
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1791
-
"type": "string"
1792
1792
}
1793
1793
},
1794
1794
"additionalProperties": false
@@ -1800,6 +1800,10 @@
1800
1800
"sidecar"
1801
1801
],
1802
1802
"properties": {
1803
+
"name": {
1804
+
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1805
+
"type": "string"
1806
+
},
1803
1807
"args": {
1804
1808
"description": "The allowed arguments for the command execution.",
1805
1809
"allOf": [
@@ -1808,10 +1812,6 @@
1808
1812
}
1809
1813
]
1810
1814
},
1811
-
"name": {
1812
-
"description": "The name for this allowed shell command configuration.\n\nThis name will be used inside of the webview API to call this command along with any specified arguments.",
1813
-
"type": "string"
1814
-
},
1815
1815
"sidecar": {
1816
1816
"description": "If this command is a sidecar command.",
1817
1817
"type": "boolean"
@@ -4938,6 +4938,22 @@
4938
4938
}
4939
4939
]
4940
4940
},
4941
+
"ShellScopeEntryAllowedArgs": {
4942
+
"description": "A set of command arguments allowed to be executed by the webview API.\n\nA value of `true` will allow any arguments to be passed to the command. `false` will disable all arguments. A list of [`ShellScopeEntryAllowedArg`] will set those arguments as the only valid arguments to be passed to the attached command configuration.",
4943
+
"anyOf": [
4944
+
{
4945
+
"description": "Use a simple boolean to allow all or disable all arguments to this command configuration.",
4946
+
"type": "boolean"
4947
+
},
4948
+
{
4949
+
"description": "A specific set of [`ShellScopeEntryAllowedArg`] that are valid to call for the command configuration.",
4950
+
"type": "array",
4951
+
"items": {
4952
+
"$ref": "#/definitions/ShellScopeEntryAllowedArg"
4953
+
}
4954
+
}
4955
+
]
4956
+
},
4941
4957
"ShellScopeEntryAllowedArg": {
4942
4958
"description": "A command argument allowed to be executed by the webview API.",
4943
4959
"anyOf": [
@@ -4952,35 +4968,19 @@
4952
4968
"validator"
4953
4969
],
4954
4970
"properties": {
4971
+
"validator": {
4972
+
"description": "[regex] validator to require passed values to conform to an expected input.\n\nThis will require the argument value passed to this variable to match the `validator` regex before it will be executed.\n\nThe regex string is by default surrounded by `^...$` to match the full string. For example the `https?://\\w+` regex would be registered as `^https?://\\w+$`.\n\n[regex]: <https://docs.rs/regex/latest/regex/#syntax>",
4973
+
"type": "string"
4974
+
},
4955
4975
"raw": {
4956
4976
"description": "Marks the validator as a raw regex, meaning the plugin should not make any modification at runtime.\n\nThis means the regex will not match on the entire string by default, which might be exploited if your regex allow unexpected input to be considered valid. When using this option, make sure your regex is correct.",
4957
4977
"default": false,
4958
4978
"type": "boolean"
4959
-
},
4960
-
"validator": {
4961
-
"description": "[regex] validator to require passed values to conform to an expected input.\n\nThis will require the argument value passed to this variable to match the `validator` regex before it will be executed.\n\nThe regex string is by default surrounded by `^...$` to match the full string. For example the `https?://\\w+` regex would be registered as `^https?://\\w+$`.\n\n[regex]: <https://docs.rs/regex/latest/regex/#syntax>",
4962
-
"type": "string"
4963
4979
}
4964
4980
},
4965
4981
"additionalProperties": false
4966
4982
}
4967
4983
]
4968
-
},
4969
-
"ShellScopeEntryAllowedArgs": {
4970
-
"description": "A set of command arguments allowed to be executed by the webview API.\n\nA value of `true` will allow any arguments to be passed to the command. `false` will disable all arguments. A list of [`ShellScopeEntryAllowedArg`] will set those arguments as the only valid arguments to be passed to the attached command configuration.",
4971
-
"anyOf": [
4972
-
{
4973
-
"description": "Use a simple boolean to allow all or disable all arguments to this command configuration.",
4974
-
"type": "boolean"
4975
-
},
4976
-
{
4977
-
"description": "A specific set of [`ShellScopeEntryAllowedArg`] that are valid to call for the command configuration.",
0 commit comments