refactor(core): allow referencing capabilities on the Tauri config file #8797
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current capability file design automatically adds all files in the capabilities folder to the application. While this is convenient for the developer, it restricts dynamic use cases (for instance plugins that are only enabled on debug or with an associated Cargo feature). After talking with @tweidinger we agreed we should add a reference on tauri.conf.json where the dev must specify which capabilities to include.
This PR adds a capabilities array inside app > security > capabilities where you can reference capabilities by identifier or inline capability objects (though this one isn't ideal since it lacks JSON schema support).
I'll open an issue later today detailing the dynamic capability implementation we can support.