postGraphGraphqlWithHttpInfo method
Ask the graph in one request, traversing.
Runs a GraphQL query against this organization's assertions. It is the one endpoint here a caller can TRAVERSE: the REST ops each answer a single question, so composing them — the entities this one points at, and what each of those resolves to — costs a request per hop with the intermediate keys held by the caller. Here that is one query and the nesting is the answer's shape. It adds no way to ask anything new. Every field runs the SAME operation the matching REST route runs, so the tenancy, the as-of bound, the traversal bounds and the conflict rule are the ones already in force; the schema is served by introspection. A query that cannot run answers 200 with an errors list, which is the wire every GraphQL client parses.
Note: This method returns the HTTP Response.
Parameters:
- GraphQLIn graphQLIn:
Implementation
Future<Response> postGraphGraphqlWithHttpInfo({ GraphQLIn? graphQLIn, }) async {
// ignore: prefer_const_declarations
final path = r'/v1/graph/graphql';
// ignore: prefer_final_locals
Object? postBody = graphQLIn;
final queryParams = <QueryParam>[];
final headerParams = <String, String>{};
final formParams = <String, String>{};
const contentTypes = <String>['application/json'];
return apiClient.invokeAPI(
path,
'POST',
queryParams,
postBody,
headerParams,
formParams,
contentTypes.isEmpty ? null : contentTypes.first,
);
}