feat(catalog): describe required and optional plugin permissions - #7
Merged
Merged
Conversation
Signed-off-by: David Viejo <dviejo@kungfusoftware.es>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add author-declared required/optional host permissions from
package.json→temps.permissionsto catalog entries. Each entry includes a known permission name, explicit required flag, and a bounded reason. Omitted metadata stays unknown; an empty list explicitly requests no host permissions. Nothing grants access automatically.Validation: 15 registry tests pass, including malformed/duplicate/unknown entries and legacy versus empty metadata. Host runtime permissions remain authoritative; this metadata describes feature requirements, not a security audit.