dynamican 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cc1cfc7f02f93e35dc7103dc3aeda6f542b87409cc83ea9a4c860a577b0bdc96
-  data.tar.gz: dadb49882f3d180376751cce2b1fecac2fd93589152ed89759e5a7a0fe5c2223
+  metadata.gz: ee2ebd9f3470a7ad1002ee3344a357fc1549e8065dffc09986f9c466577de8a9
+  data.tar.gz: e1cac4d8aa2b6f209dc6885cebe31d9ec5548af8578514aa9bf44fe1836fb697
 SHA512:
-  metadata.gz: 256b081ed7c6620a65327d9c3473610128a4ebd9e67d8dd2f5d34e1fcc99899697c932e382ddea70249acaab61372a0ab795022cee491341b0d57f77d4967055
-  data.tar.gz: '09d697b8c66f6c3257ea7b25451f71d45fd4c8730214bf579b0f4ff996b57ad8049e25b44c60d708258e4cbdbcf4c69d1cf840067f817ea9a66dd70ddd049cf3'
+  metadata.gz: 63e6761a9fed8385830c6f10697a0448ec08a8e2a781612ac54544ed810635bbfec6006c26e5054b653131a495815c6da5ed1842e11262736f9b1a274c9b0882
+  data.tar.gz: be88310e037fb8cb2e71af8f8616f1441a2963b4b65a6599762e92b6800e30cec6ede2216c5558d2ff8c8ffc7407c94e866c5894a3f8e15c31517dcb213ac5a6

data/README.md

@@ -120,3 +120,7 @@ You can apply the scope `for_action(action_name)` to Permission to find permissi
 There is a `for_item(item_name)` scope, which turns to string and then classifies automatically the argument to match it with the classified item name. The scope filters all Permission records that have an item with the specified name in its items list.
 There is also a `without_item` scope to filter records that are not linked to any item.
 As mentioned before, you can also use `conditional` and `unconditional` scopes to find objects with or without any condition attached.
+
+### Controller usage
+
+Your controllers now all have the `authorize!` method, which accepts one or two arguments: the first is the action, and the second (optional) is the item (or list of items) you want to check permissions for. As you can see, the usage is similar to the `can?` method. The reason is that is actually calls that method on the instance of `@current_user` and, whether permissions are evaluated as false, it raises an exception which is rescued by an `unauthorized` response rendered.

data/dynamican.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name        = 'dynamican'
-  s.version     = '1.0.0'
+  s.version     = '1.0.1'
   s.date        = '2020-09-10'
   s.summary     = "Dynamic permissions"
   s.description = "Dynamic and flexible database configurable permissions for your application"

data/lib/dynamican.rb

@@ -1,3 +1,4 @@
+require 'dynamican/authorization'
 require 'dynamican/evaluator'
 require 'dynamican/model'
 require 'models/dynamican/permission'

data/lib/dynamican/authorization.rb

@@ -0,0 +1,25 @@
+module Dynamican
+  module Authorization
+    extend ActiveSupport::Concern
+
+    class UnauthorizedResource < StandardError; end
+
+    included do
+      rescue_from UnauthorizedResource, with: :unauthorized
+    end
+
+    def authorize!(action, item = nil)
+      raise UnauthorizedResource unless @current_user.can? action, item
+    end
+
+    def unauthorized
+      render status: :unauthorized
+    end
+  end
+end
+
+if defined? ActiveSupport
+  ActiveSupport.on_load(:action_controller) do
+    include Dynamican::Authorization
+  end
+end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dynamican
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Valerio Bellaveglia
@@ -20,6 +20,7 @@ files:
 - README.md
 - dynamican.gemspec
 - lib/dynamican.rb
+- lib/dynamican/authorization.rb
 - lib/dynamican/evaluator.rb
 - lib/dynamican/model.rb
 - lib/generators/dynamican_migration_generator.rb