Our API platform is basically a richer GraphiQL. The concept is the same, but it displays forms for inputs and data in tables. Every query can be saved to the GraphQL Editor Cloud, in the same way the project schema is saved.
response in table format
If a query/mutation contains parameters they will be displayed as a form. This form can be customized which provides a better experience to the user than the classical gql console.
write in or use dropdown to select parameters
Sometimes the type from GraphQL is not enough to provide the correct field to the user. Our widgets are the solution to that as they provide different form fields for those situations.
use built-in widgets or import them from a library
This widget provides the date and the datetime inputs formatted to the desired format.
Same as text but masks the input.
Always provides the same value for the field.
Same as text input, but with a configurable label and placeholder.
Displays textarea
instead of input
for strings longer than input
field.
This widget helps display relations in your schema. For example: if you have to select one of the objects of type A in your form but you need to prefetch them, then you should use a relation widget. For example:
type Query{
itemsByPerson(person: String): [Item!]
people: [Person!]
}
type Item{
name: String;
owner: Person;
}
type Person{
name: String;
items: [Item!];
}
So for itemsByPerson
input, you set Query.people
as a helper to fetch People to select inside itemsByPerson
.
Autocomplete widget is better for String
completions such as map addresses.
This widget helps upload the file via the standard S3 way:
putURL
getURL
paramsputURL