Add origin and exclude-role-names filters to list-caps command #445
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
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.
This PR adds two new arguments to the
list-capscommand.Capability Origin
Fixes: #99
The first is the
--origin=attribute which allows you to specify:all(default) Returns all capabilitiesrolereturns only the capabilities inherited because a user has a roleuserreturns only the capabilities directly assigned to a user (ex: `wp user add-cap bob newcap)Exclude Role Names
The second is a flag
--exclude-role-namesthat removes a capability from the returned list if it matches the name of a role. For example, if a user has thecontributorrole, the value 'contributor' would not be returned if--exclude-role-nameswas specified, but the individual capabilities that role included, likereadwould be.