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
..
article_on_conflict_empty_update_columns.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
article_on_conflict_error_missing_article_constraint.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
article_on_conflict_ignore_constraint.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
article_on_conflict_update.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
article_unexpected_on_conflict_action.yaml	introduce v1/graphql (fix #1368) (#2064)	2019-05-10 11:35:10 +05:30
article_unexpected_on_conflict_constraint_error.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_setup.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