vigilante 1.0.11 → 1.0.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 35ad7c54344e89c133b279637c5c06041ab33863
-  data.tar.gz: 3e65f24a5a0c3591f78dd204fbe4c5574e07ad9d
+  metadata.gz: f3f96733ce7e408ff0b4898584a59e02e9de3c34
+  data.tar.gz: efc94e4ef4df468d844279310de3ce068197bea3
 SHA512:
-  metadata.gz: e45a7ef2a169fe1f47f60187ee99aee9e1b16631d1c85664e830ce58c18a1e4b703f539005ba960b60c1fdbf6be9e6ba75c6d2d113ba36d9fde11d57024a1795
-  data.tar.gz: 09855fc6392470a889b1abe7e055b704110c36551656e6caf48536304f1023339a1e2dc3a229cf9b5f1b27d5d5734aa457173353631891d989548a2c9a1fd7c0
+  metadata.gz: 7e541628b696d2f01b60a65e260dbbd20c04c7c9e0dea12289d62aeda67862d786b4d123701384a154d080d69ddcb17be09999f45a9c6aecd7ce9dd34ad30ff2
+  data.tar.gz: 2879a5834be6ba0727cf07620651eab855d93d49d06991d032a09a779414d651e429f3256616451e24977f3119b8446dc69ea9e22412a31ceaebf40bdf4971a6

data/VERSION

@@ -1 +1 @@
-1.0.11
+1.0.12

data/app/views/abilities/_ability_permission_fields.html.haml

@@ -1,10 +1,10 @@
 .nested-fields.ability-permission-fields
 
-  .row-fluid
-    .span4
+  .row
+    .col-sm-6
       #permission_from_list
-        = f.association :permission, :collection => Permission.all(:order => 'allowed_action'), :prompt => 'Choose an existing permission', :label_method => :allowed_action
-    .span4
+        = f.association :permission, :collection => Permission.order(:allowed_action), :prompt => 'Choose an existing permission', :label_method => :allowed_action
+    .col-sm-6
       #actions-on-permission{:style => 'line-height: 20px; margin-top: 5px;'}
         - if f.object.new_record?
           = link_to_add_association 'or create a new permission', f, :permission

data/app/views/abilities/show.html.haml

@@ -1,74 +1,74 @@
 
-.span6
-  %table.table
-    %tr
-      %th Name
-      %td= @ability.name
-    %tr
-      %th Description
-      %td= @ability.description
+%table.table
+  %tr
+    %th Name
+    %td= @ability.name
+  %tr
+    %th Description
+    %td= @ability.description
 
+.row
+  .col-sm-8
+    %h2 Allowed actions
 
-  %h2 Allowed actions
+    %table.table
+      - @ability.permissions.each do |perm|
+        %tr
+          %td= perm.allowed_action
 
-  %table.table
-    - @ability.permissions.each do |perm|
-      %tr
-        %td= perm.allowed_action
+    = link_to 'Edit', edit_ability_path(@ability), :class => 'btn btn-mini' if is_allowed_to?(@ability, :edit)
 
-  = link_to 'Edit', edit_ability_path(@ability), :class => 'btn btn-mini' if is_allowed_to?(@ability, :edit)
+  .col-sm-4
+    #abilities_explanation.help_text.well.small.text-muted
+      %p
+        Allowed actions are specified as follows:
 
-.span4
-  #abilities_explanation.help_text.well
-    %p
-      Allowed actions are specified as follows:
-
-    %ul
-      %li
-        %pre
-          posts[index, show]
-        %ul
-          %li
-            Only the things that are explicitly specified are allowed.
-            This declares that on the
-            %tt
-              PostsController
-            only
-            %tt
-              index
-            and
-            %tt
-              show
-            are allowed.
-      %li
-        %pre
-          *[index, show, report]
-        %ul
-          %li
-            We also allow wild-cards. Instead of a controller-name, we could write
-            %tt
-              *
-            which would mean the specified actions would apply to all controllers.
-      %li
-        %pre
-          posts[all]
-        %ul
-          %li
-            If we write
-            %tt
-              all
-            instead of a specific action or list of actions, then all actions are allowed for a given controller.
-            In this case a user has the ability to access all actions inside the posts_controller.
-      %li
-        %pre
-          *[all]
-        %ul
-          %li
-            By extension, this means a user has the ability to access all actions from all controllers.
-    %p
-      When abilities are assigned (authorisation), it is possible to specify the extent of the ability.
-      What this means depends on your website, but in case of e.g. a blog-host (like blogger), this means that a
-      %tt
-        author
-      's permissions could only be valid on those blogs he owns or has access to.
+      %ul
+        %li
+          %pre
+            posts[index, show]
+          %ul
+            %li
+              Only the things that are explicitly specified are allowed.
+              This declares that on the
+              %tt
+                PostsController
+              only
+              %tt
+                index
+              and
+              %tt
+                show
+              are allowed.
+        %li
+          %pre
+            *[index, show, report]
+          %ul
+            %li
+              We also allow wild-cards. Instead of a controller-name, we could write
+              %tt
+                *
+              which would mean the specified actions would apply to all controllers.
+        %li
+          %pre
+            posts[all]
+          %ul
+            %li
+              If we write
+              %tt
+                all
+              instead of a specific action or list of actions, then all actions are allowed for a given controller.
+              In this case a user has the ability to access all actions inside the posts_controller.
+        %li
+          %pre
+            *[all]
+          %ul
+            %li
+              By extension, this means a user has the ability to access all actions from all controllers.
+      %p
+        When abilities are assigned (authorisation), it is possible to specify the extent of the ability.
+        What this means depends on your website, but in case of e.g. a blog-host (like blogger), this means that a
+        %tt
+          author
+        's permissions could only be valid on those blogs he owns or has access to.
 

data/vigilante.gemspec

@@ -2,16 +2,16 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: vigilante 1.0.11 ruby lib
+# stub: vigilante 1.0.12 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "vigilante"
-  s.version = "1.0.11"
+  s.version = "1.0.12"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
   s.authors = ["Nathan Van der Auwera"]
-  s.date = "2016-11-07"
+  s.date = "2016-11-28"
   s.description = "Vigilante is a db-backed authorisation, completely configurable and dynamic; where permissions can be limited to extents."
   s.email = "nathan@dixis.com"
   s.extra_rdoc_files = [

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: vigilante
 version: !ruby/object:Gem::Version
-  version: 1.0.11
+  version: 1.0.12
 platform: ruby
 authors:
 - Nathan Van der Auwera
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-11-07 00:00:00.000000000 Z
+date: 2016-11-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails