-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Allow filtering for scope only #298
Comments
Already solved in v3, please upgrade. |
This is from v3 |
Ah sorry - I misread the function name ... It's for implementing the option |
No problem. I would like to help out, maybe I can create a PR this weekend. I also noticed that the new role hierarchy is powerful, but confusing. There doesn't seem to be an easy way to find out why a user has a particular role, is it global or inherited ... |
Well, every role the user has assigned will create a new document in the |
Is there anything you need to do for me to create a pull-request? This is my first and I can't seem to figure it out |
Not that I would know of ... you have to fork this project, push your code into the fork and create a pull-request ... If you're stuck there, this might help: https://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/ |
Created #299 |
Pull request to implement issue #298
Will be released as |
The Roles.getUsersInRole method always returns Roles.GLOBAL_GROUP as well as roles for a particular scope/group, which can be confusing.
A simple change in the method _getUserInRoleCursor could fix this, by accepting the option
onlyScope: true
. Now the method can be called withRoles.getUsersInRole('some-role',{scope:'some-scope', onlyScope: true})
Which will only return the users having some-role in scope some-scope now.
The text was updated successfully, but these errors were encountered: