Skip to content

Conversation

@TBThomas56
Copy link
Contributor

No description provided.

## Exploring the Schema

Click the *Docs* button (top-left) to browse the schema.
Alternatively, use Ctrl - Space inside the query editor to view available fields an options.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Alternatively, use Ctrl - Space inside the query editor to view available fields an options.
Alternatively, use Ctrl + Space inside the query editor to view available fields and options.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be being too picky

Copy link
Collaborator

@NatLeung96 NatLeung96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it worth explaining how to correctly provide variables or is that dumbing things down too much?

## Exploring the Schema

Click the *Docs* button (top-left) to browse the schema.
Alternatively, use Ctrl - Space inside the query editor to view available fields an options.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be being too picky

@TBThomas56 TBThomas56 force-pushed the tbt/docs/graphql-queries branch from 067acf8 to beb8f83 Compare November 12, 2025 13:45
@TBThomas56
Copy link
Contributor Author

Is it worth explaining how to correctly provide variables or is that dumbing things down too much?

would say that I can describe it, but how to write a query is a bit hard.

@TBThomas56 TBThomas56 force-pushed the tbt/docs/graphql-queries branch from beb8f83 to eafc8b3 Compare November 12, 2025 13:46
@VictoriaBeilsten-Edmands
Copy link
Contributor

Is it worth explaining how to correctly provide variables or is that dumbing things down too much?

That would be helpful to add.

@NatLeung96 NatLeung96 self-requested a review November 12, 2025 14:28

There are alternative clients that can be used such as [*Postman*.](https://www.postman.com/)
When configuring authorization for these tools:
- store any sensitive data (passwords, tokens) securley as variables
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

securely

For more information on how to use the GraphQL Dashboard please have a look at the official
GraphiQL docs [here](https://github.com/graphql/graphiql)

## Alternative Clients
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest removing this section

@@ -0,0 +1,85 @@
# How to Run A GraphQL Query

This guide explains how to run a GRAPHQL query for workflows using the Workflows
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This guide explains how to run a GRAPHQL query for workflows using the Workflows
This guide explains how to run a GraphQL query for workflows using the Workflows

## The Dashboard

The Workflows Dashboard includes a built-in GraphiQL client for writing and testing queries against
the GRAPHQL endppoint.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
the GRAPHQL endppoint.
the GraphQL endpoint.

The Workflows Dashboard includes a built-in GraphiQL client for writing and testing queries against
the GRAPHQL endppoint.

### iGraphQL Client
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GraphiQL?


Click the *Docs* button (top-left) to browse the schema.
The schema gives you an overview of available variables and their required types and helps build
your query as a query, mutation or subscription.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
your query as a query, mutation or subscription.
your query, mutation or subscription.

node {
name
maintainer<F6>
suite
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
suite
title

edges {
node {
name
maintainer<F6>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
maintainer<F6>
maintainer


```
query WorkflowTemplates {
workflowTemplates(limit: 4) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make more sense here to return nodes from the query as that's how we're currently using it


### Obtaining a Token
Run the following command to get a token in with the correct client id.
Please take attention to which oidc-client-id you are using.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pay attention/ take care


All queries require an *authentication token* in the request headers.

Add the following header:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a screenshot to show where the header goes.

the GraphQL endpoint which is shown below.

## Available Endpoints
[Production](https://workflows.diamond.ac.uk/graphql)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this user-facing documentation or internal documentation for Workflows developers?

Assuming that it is user-facing, should we be encouraging them to use the Workflows endpoints directly? Is it not better to encourage them to use the federated graph?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does general graph-QL documentation and tips belong here? Or is it better somewhere else like the Dev Portal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants