protector 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 03db84c2cab1a1f3ea79576688e6102d14976aa1
-  data.tar.gz: e89e5f3d0be3758a229e399a7a5696ee71572075
+  metadata.gz: 480667a8c7e66f9afb9fa1e5de46a99edc0d0325
+  data.tar.gz: 39e9914aa30962eb6792a429b10fbde0fa08b141
 SHA512:
-  metadata.gz: 1606ca8a4e1eb3683912625aec8a7366177fe377029cd05eb1f2ba4a95eaf123edd75b3ac1763101a8b60778d1c15b8fdac8a0e02c2460d084110dcdad0ca07e
-  data.tar.gz: 0a093f6600af980f34673ea75217897e29e75b5b1eef34814feea309440bb8f8f142948b8b8f1f53d75054a15fac75418eb80e0397092d79468a646601319733
+  metadata.gz: 36003bdd3337ee49372bc4cbb4e220e149ba902b47f0b5b987f31823d458cb114494f7b0b537358997fd1f73d8c1ca49fc7cfb074407f1f65e86e7f1589fa46c
+  data.tar.gz: 6874b536a5333f1e4fb4f45b08aced3c41fcd4618d7dc319ce6dcc103fd41396a8ff244d6ab34a57a9234100ee630a4dddc722fc79b48c3b92b3fec33d3c74bc

data/README.md

@@ -112,38 +112,19 @@ end
 
 ## Associations
 
-Protector is aware of associations. All the associations retrieved from restricted instance will automatically be restricted to the same context. Therefore you don't have to do anything special – it will respect proper scopes out of the box.
-
-The access to `belongs_to` kind of association depends on corresponding foreign key readability.
-
-Remember however that auto-restriction is only enabled for reading. Passing a model (or an array of those) to an association will not auto-restrict it. You should handle it manually.
-
-## Eager Loading
-
-To take a long story short: it works and you are very likely to never notice changes it introduces to the process. But it might behave unexpected (yet mathematically correct) in complex cases.
-
-Eager Loading has 2 possible strategies: JOINs and additional requests. Whenever you mark an association to preload and at the same time use this relation among `where` clause – ORMs prefer JOIN. Otherwise it goes with additional requests.
+Protector is aware of associations. All the associations retrieved from restricted instance will automatically be restricted to the same context. Therefore you don't have to do anything special – it will respect proper scopes out of the box:
 
 ```ruby
-Foo.includes(:bars)                                  # This will make 2 queries
-Foo.includes(:bars).where(bars: {absolute: true})    # This will make 1 big JOINfull query
+foo.restrict!(current_user).bar         # bar is automatically restricted by `current_user`
 ```
 
-The problem here is that JOIN strategy makes restriction scopes overlap. With the following query:
-
-```ruby
-Foo.restrict!(current_user).includes(:bars).where(bars: {absolute: true})
-```
-
-we can appear in the situation where `foos` and `bars` relations are having different restrictions scopes. In this case JOIN will filter by an intersection of scopes which is important to understand. You might not get all `Foo` entries you expect with such where clause since they might appear filtered out by the restriction scope of `Bar`.
+Remember however that auto-restriction is only enabled for reading. Passing a model (or an array of those) to an association will not auto-restrict it. You should handle it manually.
 
-If you don't want `Bar` scope to affect `Foo` selection, you can modify the query as follows:
+The access to `belongs_to` kind of association depends on corresponding foreign key readability.
 
-```ruby
-Foo.restrict!(current_user).preload(:bars).join(:bars).where(bars: {absolute: true})
-```
+## Eager Loading
 
-Such chain will force the usage of an additional request so the first query will not be scoped with `Bar` restriction.
+Both of eager loading strategies (separate query and JOIN) are fully supported.
 
 ## Manual checks and custom actions
 

data/gemfiles/AR_3.2.gemfile.lock

@@ -10,7 +10,7 @@ GIT
 PATH
   remote: /Users/inossidabile/Repos/protector
   specs:
-    protector (0.2.2)
+    protector (0.2.3)
       activesupport
       i18n
 

data/gemfiles/AR_4.gemfile.lock

@@ -9,7 +9,7 @@ GIT
 PATH
   remote: /Users/inossidabile/Repos/protector
   specs:
-    protector (0.2.2)
+    protector (0.2.3)
       activesupport
       i18n
 

data/gemfiles/Sequel.gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: /Users/inossidabile/Repos/protector
   specs:
-    protector (0.2.2)
+    protector (0.2.3)
       activesupport
       i18n
 

data/lib/protector/version.rb

@@ -1,4 +1,4 @@
 module Protector
   # Gem version
-  VERSION = "0.2.2"
+  VERSION = "0.2.3"
 end

data/lib/protector.rb

@@ -6,7 +6,7 @@ require "protector/dsl"
 require "protector/adapters/active_record"
 require "protector/adapters/sequel"
 
-I18n.load_path << Dir[File.join File.expand_path(File.dirname(__FILE__)), '..', 'locales', '*.yml']
+I18n.load_path += Dir[File.expand_path File.join('..', 'locales', '*.yml'), File.dirname(__FILE__)]
 
 Protector::Adapters::ActiveRecord.activate! if defined?(ActiveRecord)
 Protector::Adapters::Sequel.activate! if defined?(Sequel)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: protector
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - Boris Staal