role_based_authorization 0.1.6 → 0.1.7

data/README.rdoc

@@ -36,7 +36,6 @@ The library poses few and very reasonable constraints on your application. Namel
 * that your controllers provide a 'current_user' method 
 * that the user object (returned by the 'current_user' method)  implements the following two methods:
   * role: returning the role of the current user; roles can be anything (I personally use integers). This is usually implemented by adding a 'role' column to your model.
-  * description: used for logging purposes
 
 == Permission statements
 

data/VERSION

@@ -1 +1 @@
-0.1.6
+0.1.7

data/lib/role_based_authorization/role_based_authorization.rb

@@ -162,7 +162,7 @@ module RoleBasedAuthorization
     controller = controller_name  if controller.nil?  && respond_to?(:controller_name)
     
     AUTHORIZATION_LOGGER.info("user %s requested access to method %s:%s using ids:%s" %
-        [ user && user.description + "(id:#{user.id} role:#{user.role})" || 'none',
+        [ user && user.inspect + "(id:#{user.id} role:#{user.role})" || 'none',
           controller,
           action,
           ids.inspect])

data/role_based_authorization.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{role_based_authorization}
-  s.version = "0.1.6"
+  s.version = "0.1.7"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Roberto Esposito"]

data/test/role_based_authorization_test.rb

@@ -8,7 +8,6 @@ class DummyUser
   def login()               return 'test'  end  
   def role()                return  @role end
   def role=(new_role)       @role = new_role end
-  def description()         return "user" end
 end
 
 class DummyController < ActionController::Base

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: role_based_authorization
 version: !ruby/object:Gem::Version 
-  version: 0.1.6
+  version: 0.1.7
 platform: ruby
 authors: 
 - Roberto Esposito