stately_scopes 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: f3bb104f5dcf40ca69602d903253d8feda3fbbe7
-  data.tar.gz: ddbe91d6019f2c39338efd96ff62745e90ee9dec
+SHA1:
+  metadata.gz: 39563ecd6b0bf5b822ecb95b5c87a6b32a609995
+  data.tar.gz: 1537b1102caefa0190c6b7cfbf96e15a2069986b
 SHA512:
-  metadata.gz: 21f365dfa84a5f7a8360a8122a748f7bde56ba2569d6a820e25a56aed68df92b4e087264d30206b1fa287546fc15f720277454678e2830638ea357b08ec29eb8
-  data.tar.gz: 316e78a6884728885f5baa74f06aa21ff6ee4b3f3f1d9d7a6fe112a10684f82f2fae8754fa6b9238535816c9ae8864130ded365bbb76b98e8f95e92bb6a618ec
+  metadata.gz: c2b501de4a1edc32613476fe8645ae80a66c5b5819163743e4351570b8e25693e4723779b02d78c8a9ba5a7c58ba205bf9d5bbe58d687f853c93d0330626bb1f
+  data.tar.gz: dd9e57a80845d095d234176e9c93f498004a137b6d16622fde67560764d8cb9b127bacba61731658029dbdd39584616d71a3294e3b206867ecd8aa0b52831ce7

data/README.md

@@ -106,9 +106,29 @@ def upcoming?
 end
 ```
 
-Obviously this is better than hitting the database, however we'd like to write
-a test case that ensures that the new method is the equivalent of the generated
-one - so we can do something like this:
+Obviously this is always going to be better than hitting the database. The
+philosophy behind StatelyScopes is to make things easier initially, whilst
+you're still working things out.
+
+As part of updating your scopes, we recommend implementing the test behaviour
+outlined below, to best ensure that your overridden methods are providing
+the expected output.
+
+## Testing
+
+Given the aforementioned caveats, it's always in your best interests to
+(eventually) update your scopes so that you're no longer hitting the database
+for simple query methods that can be handled on the model itself.
+
+StatelyScopes gives you a nice easy way to ensure that when you do make these
+changes, that the output
+
+To test your scopes, you have access to the `.has_scoped_state?(:scope_name)` 
+method, which returns true if the model belongs to the set returned for a given
+scope.
+
+Using the example above, you might have a test which is something along these
+lines:
 
 ```ruby
 future_event = Event.create(:starts_at => 5.days.from_now)

data/lib/stately_scopes/version.rb

@@ -1,3 +1,3 @@
 module StatelyScopes
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

data/stately_scopes.gemspec

@@ -18,7 +18,7 @@ Gem::Specification.new do |spec|
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.require_paths = ["lib"]
 
-  spec.add_runtime_dependency "activerecord",   "~> 4.1.0"
+  spec.add_runtime_dependency "activerecord",   "~> 4.1"
 
   spec.add_development_dependency "bundler",    "~> 1.5"
   spec.add_development_dependency "rake"

metadata

@@ -1,83 +1,83 @@
 --- !ruby/object:Gem::Specification
 name: stately_scopes
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Nicholas Bruning
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-06-25 00:00:00.000000000 Z
+date: 2014-08-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.1.0
+        version: '4.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.1.0
+        version: '4.1'
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.5'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ~>
+    - - "~>"
       - !ruby/object:Gem::Version
         version: '1.5'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: sqlite3
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - ">="
       - !ruby/object:Gem::Version
         version: '0'
 description: I've found that when developing Rails apps, I tend to almost always pair
@@ -92,8 +92,8 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .travis.yml
+- ".gitignore"
+- ".travis.yml"
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -114,12 +114,12 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []