daedal 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,15 @@
 ---
-SHA1:
-  metadata.gz: c847bcafde8c2364dd1105418bf51ddb0f6ecd42
-  data.tar.gz: 4abb328be7b9473dec47854db2e1207cce6589e9
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    NTEzNTlhZTlmYjZkY2U0ZGY3YzhhZmNiYjdjZjljOThmM2U2MGI4Mg==
+  data.tar.gz: !binary |-
+    NTRkNGMyYjc1ZTRmYzQyZTM0ZTUzMDg4N2Y2NzI2YWYzNzQ1YzljNA==
 SHA512:
-  metadata.gz: 50cd4b1ab8720509f8b38a7968b2e1f3258d75c7fd79a3771ddf12390210e1d13d0afcbf72fe961d12d75eba477e719922e53cc17feca06fe6a94b51200d89b6
-  data.tar.gz: cab1fa56a98d7f0c3380d57af1e0a96c027235080a19ad3db38818127f610103633fb91e61169ff63ccc24c9fc1a53c406dcf96f31a11a9101872d3e6e3599d2
+  metadata.gz: !binary |-
+    ZTk5MjRmMWYyMjcyZjEzYWIyM2M4MGViYTVkYTFhNDI5NjM5OWNiMzg3MmU3
+    MTZhOTg3NzAxZWUyMTAyYTM2NzFkMWViMmY1NmU2MDE1NTdhZGM4Njg2MmVi
+    NDQyOGRlNjdkMjdjYTk0ZjVmMzBkMzI0ZDRiN2UxNzU5YTUyZjg=
+  data.tar.gz: !binary |-
+    MzA5MzBiNmU5ZWY3YTQ2YTIwMzU4ZGNlZWU0NmQ1NzA1ZTZmOTc5OTllZDZh
+    ZDI3MzBiNTdjNzY2YTQ1YWNkOTEyMmM0N2Q0Yzk4YTc5M2U5YWNhMzM5MjU5
+    MzhkNjk0MWEyOTkxZDgzNGIzOThjYzI0ZWJkNjU3Y2Q3NDM5YWQ=

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    daedal (0.0.4)
+    daedal (0.0.5)
       virtus (>= 1.0.0)
 
 GEM

data/README.md

@@ -15,7 +15,7 @@ However, elaborate queries often take the form of a complex, deeply nested hash,
 which can become difficult to create or traverse. By wrapping the core components of the
 query DSL into Ruby objects, Daedal addresses the following issues:
 
-* Constructing a large nested hash can be a headache, and using tools like `Hashie` may result in performance issues
+* Constructing a large nested hash can be a headache, and using some of the popular hash extensions may result in performance issues
 * Remembering all the optional parameters each query can take, where they reside within the query structure, and what values they can take can be challenging
 * Improperly structured queries, or queries with bad parameters, are hard to catch before sending to the server (and receiving an error)
 * Debugging invalid queries can be a grueling task

data/lib/daedal.rb

@@ -28,6 +28,7 @@ require 'daedal/filters/geo_distance_filter'
 require 'daedal/filters/and_filter'
 require 'daedal/filters/or_filter'
 require 'daedal/filters/bool_filter'
+require 'daedal/filters/nested_filter'
 
 # queries
 require 'daedal/queries/match_all_query'

data/lib/daedal/version.rb

@@ -1,3 +1,3 @@
 module Daedal
-  VERSION = '0.0.5'
+  VERSION = '0.0.6'
 end

metadata

@@ -1,27 +1,27 @@
 --- !ruby/object:Gem::Specification
 name: daedal
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Christopher Schuch
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-13 00:00:00.000000000 Z
+date: 2014-03-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: virtus
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: 1.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: 1.0.0
 description: Classes for easier ElasticSearch query creation
@@ -104,18 +104,19 @@ 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: []
 rubyforge_project: 
-rubygems_version: 2.0.6
+rubygems_version: 2.2.1
 signing_key: 
 specification_version: 4
 summary: ElasticSearch Query DSL Builders
 test_files: []
+has_rdoc: