v3.0.1

Bug fixes

• Fixed an issue that caused the linter to crash when using GraphQL v16 on a schema that had too many errors. #309 (Thanks @vojtech-dobes)

v3.0.0

Breaking changes

• graphql has been moved to peerDependencies in order to more flexible. This should help projects that were previously unable to upgrade the graphql package due to graphql-schema-linter requiring graphql v15. Usage information for this tool has been updated in the README.md to reflect this change. #298 (Thanks @dchambers)

v2.0.2

New features

• Export ValidationError to make it easier for folks to write custom rules. #271 (Thanks @vvakame)

v2.0.1

Bug fixes

• Fix a bug that prevented ignoring errors (--ignore ...) that originated from custom rules. #267 (Thanks @steverice)

v2.0.0

New rules

• interface-fields-sorted-alphabetically has been added to validate that interface fields are sorted alphabetically. #260 (Thanks @hipper)

New features

• Rules that previously verified that elements were sorted alphabetically can now be configured to check for lexicographical sort order. This is useful for folks using schema stitching and sorting their schema at runtime using graphql-js' lexicographicSortSchema. The sort order can be configured per-rule using the new rulesOptions (--rule-options) feature and specifying a different sortOrder. When unspecified, sortOrder will default to the existing behaviour: alphabetical. #256 (Thanks @dustinsgoodman)

Bug fixes

• Fix a race condition where writing to stdout on certain platforms / streams would lead to partial results or corrupted JSON. #262 (Thanks @steverice)

v1.0.1

Bug fixes

• Fix a bug that would cause graphql-schema-linter to crash when configured via package.json and ignore config was not set. #253 (Thanks @paramjitkaur)

v1.0.0

graphql-schema-linter has been in development since August 2017. During that time, 18 people have contributed 131 pull requests that make up the tool that we have today. 🎉

I believe the tool is now stable and can follow semantic versioning.

On that note, the addition or modification of existing rules will be considered a breaking change and thus will require bumping the MAJOR version of the library. By doing this, users of graphql-schema-linter won't get caught off guard by those changes.

New features

• Add support for enabling / disabling rules for parts of the GraphQL schema using the --ignore option. This works functionally the same way as inline rule overrides, but is meant to be used when adding comments to the GraphQL schema is not possible. #240 (Thanks @id-ilych)

v0.5.0

New features

• Add support for enabling / disabling rules for parts of the GraphQL schema using an inline rule override. See usage information in README.md. #237 (Thanks @mshwery)

v0.4.0

Breaking changes

• Support for comment descriptions were mistakenly dropped in v0.3.0. They were re-added in this version. #230

v0.3.0

Breaking changes

• Support for comment descriptions has been dropped in favor of descriptions defined using strings. #229
• Bumped GraphQL dependency to v15.