mirror of
https://github.com/nsnail/Ocelot.git
synced 2025-04-25 06:32:51 +08:00
aa55fe34cb
* #296 renamed configuration.json to ocelot.json in preparation * removed things we dont need for tests * another file we dont need * removed some async we dont need * refactoring to consolidate configuration code * removed another pointless abstraction * #296 started writing merge code * #296 coming up with ideas for this config merging * #296 still hacking this idea around * #296 will now do a crappy merge on the configuration * #296 change so tests pass on windows
71 lines
1.9 KiB
Markdown
71 lines
1.9 KiB
Markdown
# Ocelot using GraphQL example
|
|
|
|
Loads of people keep asking me if Ocelot will every support GraphQL, in my mind Ocelot and GraphQL are two different things that can work together.
|
|
I would not try and implement GraphQL in Ocelot instead I would either have Ocelot in front of GraphQL to handle things like authorisation / authentication or I would
|
|
bring in the awesome [graphql-dotnet](https://github.com/graphql-dotnet/graphql-dotnet) library and use it in a [DelegatingHandler](http://ocelot.readthedocs.io/en/latest/features/delegatinghandlers.html). This way you could have Ocelot and GraphQL without the extra hop to GraphQL. This same is an example of how to do that.
|
|
|
|
## Example
|
|
|
|
If you run this project with
|
|
|
|
$ dotnet run
|
|
|
|
Use postman or something to make the following requests and you can see Ocelot and GraphQL in action together...
|
|
|
|
GET http://localhost:5000/graphql?query={ hero(id: 4) { id name } }
|
|
|
|
RESPONSE
|
|
```json
|
|
{
|
|
"data": {
|
|
"hero": {
|
|
"id": 4,
|
|
"name": "Tom Pallister"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
POST http://localhost:5000/graphql
|
|
|
|
BODY
|
|
```json
|
|
{ hero(id: 4) { id name } }
|
|
```
|
|
|
|
RESPONSE
|
|
```json
|
|
{
|
|
"data": {
|
|
"hero": {
|
|
"id": 4,
|
|
"name": "Tom Pallister"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## Notes
|
|
|
|
Please note this project never goes out to another service, it just gets the data for GraphQL in memory. You would need to add the details of your GraphQL server in ocelot.json e.g.
|
|
|
|
```json
|
|
{
|
|
"ReRoutes": [
|
|
{
|
|
"DownstreamPathTemplate": "/graphql",
|
|
"DownstreamScheme": "http",
|
|
"DownstreamHostAndPorts": [
|
|
{
|
|
"Host": "yourgraphqlhost.com",
|
|
"Port": 80
|
|
}
|
|
],
|
|
"UpstreamPathTemplate": "/graphql",
|
|
"DelegatingHandlers": [
|
|
"GraphQlDelegatingHandler"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
``` |