-
-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
We accidentally introduced a CHANGELOG in [9050573] when NEWS already existed. This commit merges CHANGELOG back into NEWS, and adapts the NEWS format. [9050573]: 9050573#diff-4ac32a78649ca5bdd8e0ba38b7006a1e
- Loading branch information
1 parent
c5a6351
commit 61901dd
Showing
2 changed files
with
56 additions
and
41 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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` |