CHANGELOG.md in rspec-graphql_matchers-0.7.1 vs CHANGELOG.md in rspec-graphql_matchers-1.0.0.pre.0.1
- old
+ new
@@ -6,51 +6,71 @@
### New features
### Bug fixes
+## 1.0 (June, 2019)
+
+### Breaking changes
+
+- Support to property and hash_key matchers will be dropped on upcoming releases.
+
+### Deprecations
+
+- `.with_metadata` and `.with_property` matchers for fields will be removed on the next release.
+
+### New features
+
+- Add support for Class-based type definition api (adds support for graphql-ruby v1.8.x). Please note that `.with_metadata` and `.with_property` support has been kept but will only work on fields defined using the legacy api.
+
+### Bug fixes
+
+## 0.7.1 (July 27, 2017)
+
+Changelog fixes.
+
## 0.7.0 (July 27, 2017)
### New features
- - (#9, #8) New chainable matchers `with_property`, `with_hash_key` and `with_metadata` (Thanks to @marcgreenstock).
+- (#3, #8) New chainable matchers `with_property`, `with_hash_key` and `with_metadata` (Thanks to @marcgreenstock).
### Improvements
- - Default Raketask runs rubocop specs as well (Thanks to @marcgreenstock).
+- Default Raketask runs rubocop specs as well (Thanks to @marcgreenstock).
## 0.6.0 (July 25, 2017)
### New features
- - (PR #6) New matchers for interfaces: `expect(...).to implement(interface)` (Thanks to @marcgreenstock).
+- (PR #6) New matchers for interfaces: `expect(...).to implement(interface)` (Thanks to @marcgreenstock).
## 0.5.0 (May 10, 2017)
### New features
- - (PR #4) New matchers for mutations: `have_an_input_field` and `have_a_return_field` (Thanks to @aaronklaassen).
+- (PR #4) New matchers for mutations: `have_an_input_field` and `have_a_return_field` (Thanks to @aaronklaassen).
## 0.4.0 (Feb, 2017)
### New features
- - Improvements on error messages of have_a_field(...).of_type(...)
+- Improvements on error messages of have_a_field(...).of_type(...)
### Bug fixes
- - Fixed a bug preventing proper type checking when using matchers in the form have_a_field(fname).of_type(types.X). The bug would not happen when providing the type expectation as a string, only when using the GraphQL constants.
+- Fixed a bug preventing proper type checking when using matchers in the form have_a_field(fname).of_type(types.X). The bug would not happen when providing the type expectation as a string, only when using the GraphQL constants.
## 0.3.0 (Sep 16, 2016)
### Breaking changes
### Deprecations
### New features
-- New matcher have_field(field_name).of_type(type) for testing types and their fields
+- New matcher have_field(field_name).of_type(type) for testing types and their fields
### Bug fixes
## 0.2.0 Initial public release
@@ -58,9 +78,9 @@
### Deprecations
### New features
-- New matcher be_of_type for testing fields
-- New matcher accept_arguments for testing fields
+- New matcher be_of_type for testing fields
+- New matcher accept_arguments for testing fields
### Bug fixes