Skip to content

fix(build): validate inline capabilities from the config file - #16074

Merged
lucasfernog merged 1 commit into
devfrom
fix/validate-inline-capabilities
Sep 21, 2026
Merged

lucasfernog merged 1 commit into
devfrom
fix/validate-inline-capabilities

Conversation

@lucasfernog

Copy link
Copy Markdown
Member

Capabilities declared inline under app > security > capabilities skipped tauri-build's validation, so a typo in a permission identifier only surfaced as the generic failed to resolve ACL codegen panic. Validate the same capability set codegen resolves so the friendly "Permission X not found" error is reported instead.

Capabilities declared inline under `app > security > capabilities` skipped tauri-build's validation, so a typo in a permission identifier only surfaced as the generic `failed to resolve ACL` codegen panic. Validate the same capability set codegen resolves so the friendly "Permission X not found" error is reported instead.
@lucasfernog
lucasfernog requested a review from a team as a code owner September 21, 2026 00:13
@Legend-Master

Copy link
Copy Markdown
Contributor

Feel like we have way too much duplicated code around the config and acl handling code

@lucasfernog

Copy link
Copy Markdown
Member Author

yeah it needs a rewrite :/ tho it impacts too much code

@lucasfernog
lucasfernog merged commit fc3a810 into dev Sep 21, 2026
27 checks passed
@lucasfernog
lucasfernog deleted the fix/validate-inline-capabilities branch September 21, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants