lib/checkpoint/credential/permission.rb in checkpoint-1.0.3 vs lib/checkpoint/credential/permission.rb in checkpoint-1.1.0

- old
+ new

@@ -9,14 +9,15 @@ # The most common use from outside Checkpoint will be by way of # {Checkpoint::Query::ActionPermitted}, which will ask whether a given named # action is permitted for a user. However, Permission could be extended or # modified to implement aliasing or hierarchy, for example. # - # More likely, though, is advising the resolution of Permissions through a - # {Checkpoint::PermissionMapper} or implementing a custom - # {Checkpoint::Credential::Resolver}. Subclassing or monkey-patching Permission - # should only be necessary if the application needs to extend the actual - # behavior of the Permission objects, rather than just which ones are resolved. + # More likely, though, is advising the resolution of Permissions with a + # role map and {Checkpoint::Credential::RoleMapResolver} or implementing a + # custom {Checkpoint::Credential::Resolver}. Subclassing or monkey-patching + # Permission should only be necessary if the application needs to extend + # the actual behavior of the Permission objects, rather than just which + # ones are resolved. class Permission < Credential TYPE = 'permission' def type TYPE