graphql-engine/server/tests-py/queries/graphql_mutation/insert/geojson/insert_area.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

45 lines
968 B
YAML

- description: Insert area as a polygon
url: /v1/graphql
status: 200
response:
data:
insert_area:
returning:
- id: 1
name: Foo
area: &area
coordinates: &coords
-
- [43.75049, 11.03207]
- [43.80009, 11.03208]
- [42.60009, 10.13248]
- [43.75049, 11.03207]
type: Polygon
crs: &crs
type: name
properties:
name: 'urn:ogc:def:crs:EPSG::4326'
query:
variables:
areas:
- name: Foo
area: *area
query: |
mutation insertArea($areas: [area_insert_input!]!) {
insert_area(objects: $areas) {
returning{
id
name
area
}
}
}
- description: Delete the inserted area
url: /v1/query
status: 200
query:
type: run_sql
args:
sql: |
delete from area