types/capability: allow wildcard capability when presented in object form, add privileged-headers capability #1765
Conversation
This file contains 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
…form
At the moment, it's not possible to specify a capability as `{"resource": ["*"]}` - which is still
valid. This change also allows the explicit specification of a wildcard.
format: quotes
github-actions
bot
temporarily deployed
to
staging/pull/1765/bundle-report
VeskeR
requested changes
May 17, 2024
VeskeR
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
At the moment, it's not possible (according to TypeScript) to specify a capability as
{"resource": ["*"]}using the map-form - which is still valid. This change also allows the explicit specification of a wildcard.