access-granted 1.0.2 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ed37f3966694f5aa4708f1b12c13b079f769f6b2
-  data.tar.gz: a287e21f67658f36b532f5fe3e4c6e6ab962dbc5
+  metadata.gz: 246a35a6a2cb45ef63cc43536becfb22c88387a5
+  data.tar.gz: aae201ebfddf0b130961b0ca675863f32cc276ac
 SHA512:
-  metadata.gz: 4b25dc3178876c6134cc10b81396588c0d99cff83e320f82196f653e2db817bca124bf539acab62e8f5b01fa02e0ebb55a1253e1654d0ea55d097a6e24a0ed6e
-  data.tar.gz: 38e48bf94c3b918421316ea29d3c9b0c5b3072a44192da516a9245f6af713e239b7a656eb7ea3a23aa0048be6a844ec4d4b2be5153dcc1d60c77e554a28e78f7
+  metadata.gz: 3b8277e5bf9ad6fdd843d572c0ef707b6e4c28c7bcc4e3dd4178037320ba8bae2b58566865dfff19c4853f01e8034f4512d83321d85ecc087ca79e8d68d4d79b
+  data.tar.gz: b477974a51014c347694dd2f4000936faa2ad4f595bcab22e3dbd8e56ab5cc40f08ddeec1978241ccf66e6899680f4948435530fe5daee185a5185b6e8e3f0cd

data/README.md

@@ -48,6 +48,8 @@ Roles are defined using blocks (or by passing custom classes to keep things tidy
 **Order of the roles is VERY important**, because they are being traversed in the top-to-bottom order.
 At the top you must have an admin or other important role giving the user top permissions, and as you go down you define less-privileged roles.
 
+**I recommend starting your adventure by reading my [blog post about AccessGranted](http://blog.chaps.io/2015/11/13/role-based-authorization-in-rails.html), where I demonstrate its abilities on a real life example.**
+
 ### 1. Defining access policy
 
 Let's start with a complete example of what can be achieved:
@@ -224,7 +226,7 @@ end
 Usually you don't want to show "Create" buttons for people who can't create something.
 You can hide any part of the page from users without permissions like this:
 
-```html
+```erb
 # app/views/categories/index.html.erb
 
 <% if can? :create, Category %>

data/access-granted.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "access-granted"
-  spec.version       = "1.0.2"
+  spec.version       = "1.0.3"
   spec.authors       = ["Piotrek Okoński"]
   spec.email         = ["piotrek@okonski.org"]
   spec.description   = %q{Role based authorization gem}

data/lib/access-granted/permission.rb

@@ -20,7 +20,7 @@ module AccessGranted
     end
 
     def matches_conditions?(subject)
-      if @block
+      if @block && !subject.is_a?(Class)
         @block.call(subject, @user)
       else
         matches_hash_conditions?(subject)

data/spec/permission_spec.rb

@@ -14,6 +14,12 @@ describe AccessGranted::Permission do
       perm = subject.new(true, :read, sub.class, nil, {}, proc {|el| el.published? })
       expect(perm.matches_conditions?(sub)).to eq(true)
     end
+
+    it "does not match proc conditions when given a class instead of an instance" do
+      sub = double("Element", published?: true)
+      perm = subject.new(true, :read, sub.class, nil, {}, proc {|el| el.published? })
+      expect(perm.matches_conditions?(sub.class)).to eq(true)
+    end
   end
 
   describe "#matches_hash_conditions?" do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: access-granted
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
 platform: ruby
 authors:
 - Piotrek Okoński
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-11-20 00:00:00.000000000 Z
+date: 2015-11-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler