json_matchers 0.4.0 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ebd2f6c2a65cd0ad316c68b20ab44b7319b9fb47
-  data.tar.gz: 2a09b12a688897b183f76678991985042d3cc3db
+  metadata.gz: ae47ba6e026a29f0f498146f78039dd5b65f75cb
+  data.tar.gz: e8d728527e3010c55cdd2019376bfb2c61aa2352
 SHA512:
-  metadata.gz: c6404d6214cb53692199e0533f9b824c54feb6f3961ac34d43bfb69ce7c1212794f4e36de5fd7972aa3744d9f49318ad280798cc016d620ef215e0e3ed8545de
-  data.tar.gz: 4068995034f0ad147fe14f4640b91cfb0d8d6262f17d900daf0b91af80f87d278b2ebca054c24553d644a43ae9de1eaa0d483e38b16be0a186d4dfd3c3202138
+  metadata.gz: bbb54160e7035e4cfe4d2ae9741604fc157166f85ff431b62fdc92240cd850ae6a82b2da4fed61d9936b8a9ad65c241319f50b86f8e2f7f38ea8c0974198f559
+  data.tar.gz: 64c775526e26c009d99660e98ef7f3fbf38b0ef0cc2087d4104a48feef1edc215a8261fdf7d619ea07795da76bff5ff1071ae829ddfbb56e2f48f396652e12a2

data/NEWS.md

@@ -1,17 +1,68 @@
-# 0.2.0
+master
+======
+
+Breaking Changes
+----------------
+
+* No longer default to `strict: true`.
+
+0.4.0
+=====
+
+Breaking Changes
+----------------
+
+* Rename the gem to `json_matchers`.
+
+0.3.1
+=====
+
+* No longer condone auto-loading RSpec. Add documentation around adding `require
+  "json_matchers/rspec"` to consumers' `spec/spec_helper.rb`
+
+Breaking Changes
+----------------
+
+* Rename module to `JsonMatchers`. This resolves clashing with
+  gems like `oj` / `oj_mimic_json` that take control of the standard library's
+  `json` module. As a result, the file to require is now `json_matchers`,
+  instead of `json/matchers`.
+
+0.3.0
+=====
+
+* Pass options from matcher to `JSON::Validator`
+
+0.2.2
+=====
+
+* Includes validation failure message in RSpec output
+
+0.2.1
+=====
+
+* Supports RSpec 2 syntax `failure_message_for_should` and
+  `failure_message_for_should_not`
+
+0.2.0
+=====
 
 * RSpec failure messages include both the body of the response, and the body of
   the JSON Schema file
 
-# 0.1.0
+0.1.0
+=====
 
-## Breaking Changes
+Breaking Changes
+----------------
 
 * Remove `schema_for` in favor of using `$ref`. To learn more about `$ref`,
   check out [Understanding JSON Schema Structuring](http://spacetelescope.github.io/understanding-json-schema/structuring.html)
 
-# 0.0.1
+0.0.1
+=====
 
-## Features
+Features
+--------
 
 * Validate your Rails response JSON with `match_response_schema`

data/README.md

@@ -41,12 +41,16 @@ Define your [JSON Schema](http://json-schema.org/example1.html) in the schema di
   "type": "object",
   "required": ["posts"],
   "properties": {
-    "type": "object",
-    "required": ["id", "title", "body"],
-    "properties": {
-      "id": { "type": "integer" },
-      "title": { "type": "string" },
-      "body": { "type": "string" }
+    "posts": {
+      "type": "array",
+      "items":{
+        "required": ["id", "title", "body"],
+        "properties": {
+          "id": { "type": "integer" },
+          "title": { "type": "string" },
+          "body": { "type": "string" }
+        }
+      }
     }
   }
 }
@@ -69,7 +73,7 @@ end
 
 ### Passing options to the validator
 
-The matcher accepts options, which it'll pass to the validator:
+The matcher accepts options, which it passes to the validator:
 
 ```ruby
 # spec/requests/posts_spec.rb
@@ -79,7 +83,7 @@ describe "GET /posts" do
     get posts_path, format: :json
 
     expect(response.status).to eq 200
-    expect(response).to match_response_schema("posts", strict: false)
+    expect(response).to match_response_schema("posts", strict: true)
   end
 end
 ```

data/lib/json_matchers/matcher.rb

@@ -10,14 +10,10 @@ module JsonMatchers
     def matches?(response)
       @response = response
 
-      validator_options = {
-        strict: true,
-      }.merge(options)
-
       JSON::Validator.validate!(
         schema_path.to_s,
         response.body,
-        validator_options,
+        options,
       )
     rescue JSON::Schema::ValidationError => ex
       @validation_failure_message = ex.message

data/lib/json_matchers/version.rb

@@ -1,3 +1,3 @@
 module JsonMatchers
-  VERSION = "0.4.0"
+  VERSION = "0.5.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: json_matchers
 version: !ruby/object:Gem::Version
-  version: 0.4.0
+  version: 0.5.0
 platform: ruby
 authors:
 - Sean Doyle
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-02 00:00:00.000000000 Z
+date: 2015-11-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json-schema
@@ -104,7 +104,6 @@ files:
 - ".gitignore"
 - ".rspec"
 - ".travis.yml"
-- CHANGELOG.md
 - CONTRIBUTING.md
 - Gemfile
 - LICENSE.txt
@@ -140,7 +139,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.8
+rubygems_version: 2.5.0
 signing_key: 
 specification_version: 4
 summary: Validate your Rails JSON API's JSON

data/CHANGELOG.md

@@ -1,34 +0,0 @@
-master
-------
-
-0.4.0
------
-
-* BREAKING CHANGE: Rename the gem to `json_matchers`.
-
-0.3.1
------
-
-* BREAKING CHANGE: Rename module to `JsonMatchers`. This resolves clashing with
-  gems like `oj` / `oj_mimic_json` that take control of the standard library's
-  `json` module. As a result, the file to require is now `json_matchers`,
-  instead of `json/matchers`.
-
-* No longer condone auto-loading RSpec. Add documentation around adding `require
-  "json_matchers/rspec"` to consumers' `spec/spec_helper.rb`
-
-0.3.0
------
-
-* Pass options from matcher to `JSON::Validator`
-
-0.2.2
------
-
-* Includes validation failure message in RSpec output
-
-0.2.1
------
-
-* Supports RSpec 2 syntax `failure_message_for_should` and
-  `failure_message_for_should_not`