dead_simple_authorization 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 094811cb3c6a7c29d7de9eaf841554e4179d2919
-  data.tar.gz: 493f517f366e9f935de8c848879639154cda8e88
+  metadata.gz: 15a49f312a875cba52fd7ea632d824de59c15056
+  data.tar.gz: 797ddf01b6afd02fa40d97b46053c5997e518e04
 SHA512:
-  metadata.gz: b99b566cad0ec612eb2a71b2dcb6a1d35856943fade47fe092426e536929be1af09bf429686bd5e5dc2db8631be50e3cc81556ed1f8084b54c4c34552e774487
-  data.tar.gz: 09b0919c5faa86f439ac8f850d7777c4c9ac59af366824e07f4d87396bd71e79add34afe2909fdcc7a4097c278f7980f1b671cc4dbe6b4f1529c820122057ed4
+  metadata.gz: d27a36a1dc76c1f92b7ebea11da3cd900bb1ddb1a572db8b84a2fecd5adcac46846a78bc8a85d7db7077b66117a091fb739f189c820b5a04653597b77f7deb17
+  data.tar.gz: ff5f5b0eb38c6baa2b8d3341925b1836b3e9dac4d3e30d8e76d3a904ccdd8efff28d1d967cc313199ef0e5a9a54d571b362ac6e09b41a65c83c9c02aca283612

data/README.md

@@ -4,7 +4,7 @@
 It's a simple gem for authorization. The main concepts around dead_simple_authorization are: users, resources and permissions. Using a couple of simple naming conventions, it organizes the way in which access to a resource (an activerecord model for example) by a user (e.g. a web application's user) is checked.
 
 ## What's included
-The juice of this gems are the methods can? and authorize included in the module DeadSimpleAuthorization::Helpers. Both methods accept 3 arguments: a user, an action and a resource. For example can?(user, :update, post) checks if a user has the permission to update a post. The authorize method is the stricter of the two, as if the user doesn't have permission, it raises a DeadSimpleAuthorization::Errors::NotAuthorized error, while can? method only returns a boolean.
+The juice of this gem are the methods can? and authorize included in the module DeadSimpleAuthorization::Helpers. Both methods accept 3 arguments: a user, an action and a resource. For example can?(user, :update, post) checks if a user has the permission to update a post. The authorize method is the stricter of the two, as if the user doesn't have permission, it raises a DeadSimpleAuthorization::Errors::NotAuthorized error, while can? method only returns a boolean.
 
 ## Example usage
 Think of a web application (e.g. a rails app), a blog for example, where there are Users and Posts and a user can be the owner of a Post. How would we create a simple authorization mechanism in this case?

data/lib/dead_simple_authorization/helpers.rb

@@ -24,10 +24,10 @@ module DeadSimpleAuthorization
     # error, but returns the boolean outcome of the check
     #
     def can?(user, action, resource)
-      action = action.to_sym if action.is_a? String
+      action = action.to_s
       policy_class = "#{resource.class}Policy"
       policy = Object::const_get(policy_class).new(resource, user)
-      policy.send("#{action.to_s}?")
+      policy.send("#{action}?")
     end
   end
 end

data/lib/dead_simple_authorization/version.rb

@@ -1,3 +1,3 @@
 module DeadSimpleAuthorization
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dead_simple_authorization
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Pantelis Vratsalis
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-03-06 00:00:00.000000000 Z
+date: 2015-07-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -93,10 +93,11 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.4.5
 signing_key: 
 specification_version: 4
 summary: A pretty simple solution for permissions on resources - framework agnostic
 test_files:
 - spec/helpers_spec.rb
 - spec/spec_helper.rb
+has_rdoc: