Contents

# Changelog

### Breaking changes

### Deprecations

### New features

### Bug 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).

### Improvements

  - 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).

## 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).

## 0.4.0 (Feb, 2017)

### New features

 - 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.

## 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

### Bug fixes

## 0.2.0 Initial public release

### Breaking changes

### Deprecations

### New features

- New matcher be_of_type for testing fields
- New matcher accept_arguments for testing fields

### Bug fixes

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
rspec-graphql_matchers-0.7.1	CHANGELOG.md