Skip to content

Update from master #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 105 commits into from
Feb 12, 2018
Merged

Update from master #2

merged 105 commits into from
Feb 12, 2018

Conversation

giautm
Copy link
Owner

@giautm giautm commented Feb 12, 2018

No description provided.

freiksenet and others added 29 commits January 2, 2018 14:50
Added subscriptions support to makeRemoteExectuableSchema
…attern in new GraphQL SDL (#559)

* #64 - Update docs and tests to reflect new strings-as-descriptions pattern in new GraphQL SDL

* Make tests compatible with graphql v0.11

* Fix test errors

* Remove extra space

* Fix review comments
* Update schemaRecreation.ts

`mergeSchemas` does not set `astNode` properties, when recreating types.
But `CacheControlExtension.willResolveField` uses the `astNode` property in order to get the `cacheControl` directives.
* Allow IEnumResolver values to be number type
…rfaces (#546)

* add failing test for multi interface issue

* interface / interface always implements an abstract type

* changelog

* the linter always should be happy

* Update CHANGELOG.md
Remove graphql-subscriptions from devDependencies
* Also recreate astNode for fields

In a [previous commit](fd9f626) we added the `astNode` property in the `reacreateCompositeType` function. That resulted in cache control working with schema stitching but only for GraphQL Types. By recreating the `astNode` prop also in `fieldToFieldConfig` cache control also works for fields. This is required for caching fields and hence queries.

* Add ast to input field node too
…609)

* fix(subscriptions): The subscription resolvers were firing too often

The underlying subscription in a remote schema was not terminated properly, causing memory leaks. In
addition, multiple subscriptions caused duplicate payloads. Both is fixed by removing the PubSub
dependency and directly transforming the Observer returned by the ApolloLink to an async iterable.
This allows the async iterable to propagate to the underlying observable to cancel the suscription
once the subscription is not needed anymore.

* refactor(test): remove timeout from test

* chore(changelog): add fix to changelog
* add tests demonstrating bug with var generation

* add deduping of new variable definitions when delegating to schemas

* update changelog.md
* Allow passing an array of resolver functions to makeExecutable schema

- Closes #486

* Implement passing an array of resolvers sets to mergeSchemas

* Introduce unit or array composite type

* Fix @types dep

* Fix resolvers to accept and move forward args with zero or false values (#586)

Fixing the args with zero value or false

* Also recreate astNode for fields (#580)

* Also recreate astNode for fields

In a [previous commit](fd9f626) we added the `astNode` property in the `reacreateCompositeType` function. That resulted in cache control working with schema stitching but only for GraphQL Types. By recreating the `astNode` prop also in `fieldToFieldConfig` cache control also works for fields. This is required for caching fields and hence queries.

* Add ast to input field node too

* Address comments, remove lodash

* Fix @types dep

* Fix resolvers to accept and move forward args with zero or false values (#586)

Fixing the args with zero value or false

* Also recreate astNode for fields (#580)

* Also recreate astNode for fields

In a [previous commit](fd9f626) we added the `astNode` property in the `reacreateCompositeType` function. That resulted in cache control working with schema stitching but only for GraphQL Types. By recreating the `astNode` prop also in `fieldToFieldConfig` cache control also works for fields. This is required for caching fields and hence queries.

* Add ast to input field node too

* Address comments, remove lodash

* Use mergeDeep instead of lodash.merge

* Fix build

* Changelog and separate utility

* Update CHANGELOG
* Recreate enums and scalars in mergeSchema
…k-http (#621)

* fix(schema-stitching): Pass through error when coming from apollo-link-http

This is needed in order to handle custom properties on the GraphQLError object, like `code` or
`requestId`

* refactor(schema-stitching): Remove redundant type information

* chore(changelog): Add PR to changelog
@giautm giautm merged commit 53b2d4d into giautm:master Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.