hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 08:02:15 +03:00
Code Issues Projects Releases Wiki Activity

update remote schema doc (#2149)

Browse Source
This commit is contained in:
Arpit Kushwaha 2019-05-09 16:10:41 +05:30 committed by Shahidh K Muhammed
parent 3080100d8f
commit d942266c59
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
remote-schemas.md
View File

@ -6,7 +6,7 @@ Merge remote GraphQL schemas with GraphQL Engine's Postgres-based schema to quer
* Supporting features like payments, etc. and providing a consistent interface to access them i.e. behind the GraphQL Engine's API
* Fetching disparate data from other sources (*e.g. from a weather API or another database*)
To support custom business logic, you'll need to create a custom GraphQL server (see [boilerplates](community/boilerplates/graphql-servers)) and merge its schema with GraphQL Engine's.
To support custom business logic, you'll need to create a custom GraphQL server (see [boilerplates](community/boilerplates/remote-schemas)) and merge its schema with GraphQL Engine's.
![remote schems architecture](assets/remote-schemas-arch.png)
@ -69,7 +69,6 @@ Please note that boilerplates for more languages, frameworks, serverless platfor
* Nomenclature: Type names and node names need to be unique across all merged schemas (case-sensitive match). In the next few iterations, support for merging types with the exact same name and structure will be available.
* Nodes from different GraphQL servers cannot be used in the same query/mutation. All top-level nodes have to be from the same GraphQL server.
* Subscriptions on remote GraphQL server are not supported.
* Interfaces are not supported - if a remote schema has interfaces, an error will be thrown if you try to merge it.
These limitations will be addressed in upcoming versions.