Created
September 15, 2012 19:23
-
-
Save ryanb/3729390 to your computer and use it in GitHub Desktop.
How you can break up large Ability class in CanCan
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
module Abilities | |
def self.ability_for(user) | |
if user.admin? | |
AdminAbility.new(user) | |
else user | |
MemberAbility.new(user) | |
else | |
GuestAbility.new | |
end | |
end | |
class AdminAbility | |
include CanCan::Ability | |
def initialize(user) | |
# ... | |
end | |
end | |
class MemberAbility | |
include CanCan::Ability | |
def initialize(user) | |
# ... | |
end | |
end | |
class GuestAbility | |
include CanCan::Ability | |
def initialize(user) | |
# ... | |
end | |
end | |
# move classes into separate files as needed if they get too long | |
end |
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
def current_ability | |
@current_ability ||= Abilities.ability_for(current_user) | |
end |
How would you do if some permissions are not mutually exclusive ..?
An example from @dgilperez using Ability#merge.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for this! How would you do if some permissions are not mutually exclusive - i.e. a
User
has different roles? For example, an Admin should have permissions defined inAdminAbility
and also the ones inMemberAbility
.