-
Notifications
You must be signed in to change notification settings - Fork 16
WIP: Allow creating per bundle/ per group roles #209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
amitaibu
wants to merge
5
commits into
default-roles
Choose a base branch
from
208-override-roles
base: default-roles
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b63f027
Rename OG field to RolesOverride
amitaibu 699a3a5
createRoles should accept also group IDs
amitaibu 1b4272a
Revert "createRoles should accept also group IDs"
amitaibu e70626a
Revert "Revert "createRoles should accept also group IDs""
amitaibu 96f6ff2
Add perGroup and perBundle create role methods
amitaibu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pfrenssen I guess it is a bit ugly having to pass either bundle ID or group ID. Which made me thing that maybe we should have two Og Roles bundles:
per_bundleandper_groupso the schema will just have those two keys:group_typeandreference_id(bad name) .reference_idwill be populated either with the bundle ID or the group ID.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OgRoleis a config entity, I don't think this supports bundles. If you look at the inherited methodOgRole::bundle()you see it returns the entity type instead of the bundle. Only content entities support custom bundles out of the box.But I actually think we can hack in bundle support easily. We just need to ensure that the bundle is stored along with the entity, that we have a
$this->bundleproperty that we populate in the constructor, and then we can use it to handleper_bundleandper_groupspecific logic.