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
..
author_article.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
insert_into_array_col_with_array_input.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
insert_various_postgres_types.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
order_col_shipped_null.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
person_jsonb_array.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
person_jsonb_variable_array.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
person_jsonb_variable.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
person_jsonb.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
schema_setup.yaml	run graphql tests on both http and websocket; add parallelism (close #1868) (#1921)	2019-04-08 12:52:38 +05:30
schema_teardown.yaml	run graphql tests on both http and websocket; add parallelism (close #1868) (#1921)	2019-04-08 12:52:38 +05:30
values_teardown.yaml	run graphql tests on both http and websocket; add parallelism (close #1868) (#1921)	2019-04-08 12:52:38 +05:30