Socket
Socket
Sign inDemoInstall

merge-graphql-schemas

Package Overview
Dependencies
Maintainers
2
Versions
269
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

merge-graphql-schemas - npm Package Compare versions

Comparing version 1.1.4 to 1.2.0

4

CHANGELOG.md

@@ -9,2 +9,6 @@ # Change Log

## [1.2.0] - 2017-10-17
### Added
- Added TypeScript support to fileLoader. Thanks to [@dotansimha](https://github.com/dotansimha) [PR #95](https://github.com/okgrow/merge-graphql-schemas/pull/95
## [1.1.4] - 2017-09-15

@@ -11,0 +15,0 @@ ### Added

@@ -423,2 +423,3 @@ 'use strict';

switch (pathObj.ext) {
case '.ts':
case '.js':

@@ -425,0 +426,0 @@ {

@@ -417,2 +417,3 @@ import fs from 'fs';

switch (pathObj.ext) {
case '.ts':
case '.js':

@@ -419,0 +420,0 @@ {

2

package.json
{
"name": "merge-graphql-schemas",
"author": "OK GROW!",
"version": "1.1.4",
"version": "1.2.0",
"description": "A utility library to facilitate merging of modularized GraphQL schemas and resolver objects.",

@@ -6,0 +6,0 @@ "repository": {

@@ -257,3 +257,3 @@ # Merge Graphql Schemas

If you are using `graphqlHTTP` you don't need to separate the resolver into `Query/Mutation/Subscrition`, otherwise it won't work. The resolvers should look like the following:
If you are using `graphqlHTTP` you don't need to separate the resolver into `Query/Mutation/Subscription`, otherwise it won't work. The resolvers should look like the following:

@@ -260,0 +260,0 @@

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc