petergate 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c3955dd64ab0e68946033b9f5b28adc57a3bbe0e
-  data.tar.gz: bf67e237b5bf27e5bf2f3e6dd96fbb09096cf7df
+  metadata.gz: 02fcc936703a7764d3e360c97fd577d2bb9c2ff2
+  data.tar.gz: 0d71fa88703d732bd82a790ae16eae8e1c6890ad
 SHA512:
-  metadata.gz: 586c85235b3d327142b98abf32550ab445e4cb81cc129baba6bb9f8129e1f0e6da07dc75444ee0ca51dd82c2a4b35ef9f6c01dfa94f20720bb3b51c3553403f5
-  data.tar.gz: 9a713a1a3529f83794c8fb8023bc5b1a1b7b640f5b50c2097920039bbb89e594a7bcff3dc7637b79774792b1d8417a994b3874c23f9f872d4c62d80915b77b63
+  metadata.gz: 906c4d8507b98f3bc0e8b512bf6e878f07e4757c63795091408775e4fdc480caf6c31fd4b8210d26ec6584ff37f9735432cb0a7b0b5bfe8cfbad9f752cecbe1b
+  data.tar.gz: 5f0622280f7d006c159f5fda9881de0f6ef4bea4d69d8bdd25ad7f3a0e391704a9ffedefcc6e83b9ca2b9957b618225391ca55b2640175c104dac0ffe71f14f9

data/README.md

@@ -53,7 +53,7 @@ Usage
 Setup permissions in your controllers the same as you would for a before filter like so:
 
 ```ruby
-access all: [:show, :index], user: AllRest
+access all: [:show, :index], user: ALLREST
 ```
 
 Inside your views you can use logged_in?(:admin, :customer, :etc) to show or hide content.
@@ -68,7 +68,8 @@ If you need to access available roles within your project you can by calling:
 User::ROLES
 # or from an instance
 User.first.available_roles
-# ROLES is a CONSTANT and will still work from within the User model instance methods like in this default setter:
+# ROLES is a CONSTANT and will still work from within the User model instance methods
+# like in this default setter:
 
 def roles=(v)
   self[:roles] = v.map(&:to_sym).to_a.select{|r| r.size > 0 && ROLES.include?(r)}

data/lib/petergate.rb

@@ -4,6 +4,12 @@ require "petergate/railtie"
 module Petergate
   module ControllerMethods
     module ClassMethods
+      def const_missing(const_name)
+        super unless const_name == :AllRest
+        warn "`AllRest` has been deprecated. Use `ALLREST` instead."
+        ALLREST
+      end
+
       def access(rules = {}, &block)
         if block
           b_rules = block.call
@@ -27,7 +33,7 @@ module Petergate
     end
 
     # Look into using Controller.action_methods instead
-    AllRest = [:show, :index, :new, :edit, :update, :create, :destroy]
+    ALLREST = [:show, :index, :new, :edit, :update, :create, :destroy]
 
     def self.included(base)
       base.extend(ClassMethods)

data/lib/petergate/version.rb

@@ -1,3 +1,3 @@
 module Petergate
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

data/petergate.gemspec

@@ -19,5 +19,5 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 1.7"
   spec.add_development_dependency "rake", "~> 10.0"
-  spec.add_dependency 'activerecord', "~> 4.1.7"
+  spec.add_dependency 'activerecord', "> 4.0.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: petergate
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Isaac Sloan
@@ -42,16 +42,16 @@ dependencies:
   name: activerecord
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">"
       - !ruby/object:Gem::Version
-        version: 4.1.7
+        version: 4.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">"
       - !ruby/object:Gem::Version
-        version: 4.1.7
+        version: 4.0.0
 description: If you like the straight forward and effective nature of Strong Parameters
   and suspect that CanCan might be overkill for your project then you'll love Petergate's
   easy to use and read action and content based authorizations.