graphql-engine/server/tests-py/queries/graphql_mutation/insert/geojson/insert_compounds.yaml
Anon Ray a21f6cd648 introduce v1/graphql (fix #1368) (#2064)
Changes compared to `/v1alpha1/graphql`

* Changed all graphql responses in **/v1/graphql** endpoint to be 200. All graphql clients expect responses to be HTTP 200. Non-200 responses are considered transport layer errors. 

* Errors in http and websocket layer are now consistent and have similar structure.
2019-05-10 11:35:10 +05:30

53 lines
1.3 KiB
YAML

- description: Insert the path for a road
url: /v1/graphql
status: 200
response:
data:
insert_compounds:
returning:
- user_id: 1
name: foo
areas: &areas
type: MultiPolygon
coordinates:
- - - [43.75049, 11.03207]
- [43.80009, 11.03208]
- [43.90009, 11.03308]
- [43.75049, 11.03207]
- - [43.75049, 11.03207]
- [41.60009, 21.03208]
- [41.70009, 21.03308]
- [43.75049, 11.03207]
- - - [23.75049, 31.03207]
- [23.80009, 31.03208]
- [23.80009, 31.03308]
- [23.75049, 31.03207]
crs: &crs
type: name
properties:
name: 'urn:ogc:def:crs:EPSG::4326'
query:
variables:
compounds:
- user_id: 1
name: foo
areas: *areas
query: |
mutation insertCompounds($compounds: [compounds_insert_input!]!) {
insert_compounds(objects: $compounds) {
returning{
user_id
name
areas
}
}
}
- description: Delete the inserted compounds
url: /v1/query
status: 200
query:
type: run_sql
args:
sql: |
delete from compounds