vayacondios-client 0.3.1 → 0.3.2

data/Gemfile

@@ -2,6 +2,8 @@ source 'https://rubygems.org'
 
 # em-mongo is too loose with its dependencies; 2.0.0 bson breaks vcd
 gem 'bson', '1.9.2'
+# cookiejar 0.3.1 has busted file permissions WTF
+gem 'cookiejar', '0.3.0'
 
 gemspec name: 'vayacondios-server'
 gemspec name: 'vayacondios-client'

data/features/events.feature

@@ -86,6 +86,146 @@ Feature: Events
     ]
     """
 
+  Scenario: Retrieving Existing Events with a Limit Query
+    Given the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id1",
+      "_t": "2012-02-13T12:34:42.452Z",
+      "_d": {
+        "alignment": "good"
+      }
+    }
+    """
+    And   the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id2",
+      "_t": "2012-02-13T12:34:42.452Z",
+      "_d": {
+        "alignment": "evil"
+      }
+    }
+    """
+    When  the client sends a GET request to "/v3/organization/events/topic" with the following body:
+    """
+    {
+      "sort": "alignment",
+      "order": "desc",
+      "limit": 1
+    }
+    """
+    Then  the response status should be 200
+    And   the response body should be:
+    """
+    [
+      {
+        "id": "id1",
+        "time": "2012-02-13T12:34:42.452Z",
+        "alignment": "good"
+      }
+    ]
+    """
+
+  Scenario: Retrieving Existing Events with a Sort Query
+    Given the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id1",
+      "_t": "2012-02-13T12:34:43.452Z",
+      "_d": {
+        "alignment": "good"
+      }
+    }
+    """
+    And   the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id2",
+      "_t": "2012-02-13T12:34:42.452Z",
+      "_d": {
+        "alignment": "neutral"
+      }
+    }
+    """
+    And   the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id3",
+      "_t": "2012-02-13T12:34:45.452Z",
+      "_d": {
+        "alignment": "evil"
+      }
+    }
+    """
+    When  the client sends a GET request to "/v3/organization/events/topic" with the following body:
+    """
+    {
+      "sort": "alignment",
+      "order": "asc"
+    }
+    """
+    Then  the response status should be 200
+    And   the response body should be:
+    """
+    [
+      {
+        "id": "id3",
+        "time": "2012-02-13T12:34:45.452Z",
+        "alignment": "evil"
+      },
+      {
+        "id": "id1",
+        "time": "2012-02-13T12:34:43.452Z",
+        "alignment": "good"
+      },
+      {
+        "id": "id2",
+        "time": "2012-02-13T12:34:42.452Z",
+        "alignment": "neutral"
+      }
+    ]
+    """
+
+  Scenario: Retrieving Existing Events with a Fields Query
+    Given the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id1",
+      "_t": "2012-02-13T12:34:42.452Z",
+      "_d": {
+        "alignment": "good"
+      }
+    }
+    """
+    And   the following Event exists under topic "topic" in the database:
+    """
+    {
+      "_id": "id2",
+      "_t": "2012-02-13T12:34:42.452Z",
+      "_d": {
+        "alignment": "evil"
+      }
+    }
+    """
+    When  the client sends a GET request to "/v3/organization/events/topic" with the following body:
+    """
+    {
+      "alignment": "good",
+      "fields": ["alignment", "id"]
+    }
+    """
+    Then  the response status should be 200
+    And   the response body should be:
+    """
+    [
+      {
+        "id": "id1",
+        "alignment": "good"
+      }
+    ]
+    """
+
   Scenario: Creating Events
     Given there are no Events under topic "topic" in the database
     When  the client sends a POST request to "/v3/organization/events/topic" with no body
@@ -136,7 +276,7 @@ Feature: Events
     }
     """
     And   there are no Events under topic "topic" in the database
-  
+
   Scenario: Deleting Events with a Time Query
     Given the following Event exists under topic "topic" in the database:
     """
@@ -157,7 +297,7 @@ Feature: Events
     When  the client sends a DELETE request to "/v3/organization/events/topic" with the following body:
     """
     {
-      "after": "2012-01-01T00:00:00.000Z"     
+      "after": "2012-01-01T00:00:00.000Z"
     }
     """
     Then  the response status should be 200

data/features/stashes.feature

@@ -49,21 +49,30 @@ Feature: Stashes
     """
     {
       "_id": "topic",
-      "root": { 
+      "root": {
         "b": 1
       }
     }
     """
+    And the following Stash exists in the database:
+    """
+    {
+      "_id": "topic",
+      "root": {
+        "b": 5
+      }
+    }
+    """
     When  the client sends a GET request to "/v3/organization/stashes" with the following body:
     """
-    { 
-      "root.b": 1 
+    {
+      "root.b": 1
     }
     """
     Then  the response status should be 200
     And   the response body should be:
     """
-    [ 
+    [
       {
         "topic": "topic",
         "root": {
@@ -88,7 +97,7 @@ Feature: Stashes
     """
     When  the client sends a GET request to "/v3/organization/stashes" with the following body:
     """
-    { 
+    {
       "root.b": 1,
       "fields": ["root.a"]
     }
@@ -108,6 +117,98 @@ Feature: Stashes
     ]
     """
 
+  Scenario: Retrieving Stashes using Sorting
+    Given the following Stash exists in the database:
+    """
+    {
+      "_id": "topic1",
+      "root": {
+        "a": {
+          "foo": 3
+        },
+        "b": 1
+      }
+    }
+    """
+    And the following Stash exists in the database:
+    """
+    {
+      "_id": "topic2",
+      "root": {
+        "a": {
+          "foo": 2
+        },
+        "b": 1
+      }
+    }
+    """
+    When  the client sends a GET request to "/v3/organization/stashes" with the following body:
+    """
+    {
+      "root.b": 1,
+      "sort": "root.a.foo",
+      "order": "asc"
+    }
+    """
+    Then  the response status should be 200
+    And   the response body should be:
+    """
+    [
+      {
+        "topic": "topic2",
+        "root": {
+          "a": {
+            "foo": 2
+          },
+          "b": 1
+        }
+      },
+      {
+        "topic": "topic1",
+        "root": {
+          "a": {
+            "foo": 3
+          },
+          "b": 1
+        }
+      }
+    ]
+    """
+
+  Scenario: Retrieving Stashes using Limits
+    Given the following Stash exists in the database:
+    """
+    {
+      "_id": "topic1",
+      "b": 1
+    }
+    """
+    And the following Stash exists in the database:
+    """
+    {
+      "_id": "topic2",
+      "b": 1
+    }
+    """
+    When  the client sends a GET request to "/v3/organization/stashes" with the following body:
+    """
+    {
+      "b": 1,
+      "limit": 1,
+      "order": "desc"
+    }
+    """
+    Then  the response status should be 200
+    And   the response body should be:
+    """
+    [
+      {
+        "topic": "topic2",
+        "b": 1
+      }
+    ]
+    """
+
   Scenario: Creating Stashes without a Query
     Given there are no matching Stashes in the database
     When  the client sends a POST request to "/v3/organization/stashes" with no body

data/lib/vayacondios.rb

@@ -3,7 +3,7 @@ module Vayacondios
   API_VERSION            = 'v3'
 
   # Gem version for both client and server
-  GEM_VERSION            = '0.3.1'
+  GEM_VERSION            = '0.3.2'
 
   # Default port to find/connect to for the server
   DEFAULT_SERVER_PORT    = 3467

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vayacondios-client
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.3.2
   prerelease: 
 platform: ruby
 authors:
@@ -13,7 +13,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-20 00:00:00.000000000 Z
+date: 2014-03-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: configliere
@@ -152,7 +152,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -3803035025885322976
+      hash: -2388885821583862613
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -161,7 +161,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -3803035025885322976
+      hash: -2388885821583862613
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23