graphql-schemax - npm Package Compare versions

Comparing version 0.0.6 to 0.0.7

CHANGELOG.md

		@@ -5,2 +5,4 @@ # Changelog

		### [0.0.7](https://github.com/nicolasdao/graphql-schemax/compare/v0.0.6...v0.0.7) (2021-10-21)

		### [0.0.6](https://github.com/nicolasdao/graphql-schemax/compare/v0.0.5...v0.0.6) (2021-10-21)
		@@ -7,0 +9,0 @@

package.json

		{
		"name": "graphql-schemax",
		"version": "0.0.6",
		"version": "0.0.7",
		"description": "Creates GraphQL string schema from plain JSON objects.",
		@@ -5,0 +5,0 @@ "keywords": [

README.md

		@@ -110,2 +110,3 @@ # GRAPHQL-SCHEMAX
		> - [How to merge schemas?](#how-to-merge-schemas)
		> - [What happens when the same type definitions exist in multiple schemas?](#what-happens-when-the-same-type-definitions-exist-in-multiple-schemas)
		> * [License](#license)
		@@ -619,3 +620,3 @@

		Mutates the `Schemax` instance by adding more schemas definitions. It supports the same signature as the [`constructore`](#constructor).
		Mutates the `Schemax` instance by adding more schema definitions. It supports the same signature as the [`constructor`](#constructor).

		@@ -737,3 +738,3 @@ ```js

		They are merged in a single type definition. This is how the `type Query`, `type Mutation` and `type Subscription` can be defined in multiple microservice schema and merged into a single GraphQL schema. For example:
		They are merged in a single type definition. This is how the `type Query`, `type Mutation` and `type Subscription` can be defined in multiple microservice schemas and merged into a single GraphQL schema. For example:

		@@ -740,0 +741,0 @@ ```js

New alerts