GraphQL Client & Explorer

A GraphiQL-style window with a query editor, variables and response panes; it returns built-in sample data and never contacts the endpoint.

packages/graphql-client

GraphQL Client has the layout of a GraphQL explorer: an endpoint field (default http://localhost:8443/graphql), a GraphQL Query / Mutation editor, Query Variables (JSON), a Schema Documentation panel and a JSON Response pane with a status line.

The request is not sent. gql-execute in main.js waits about 160 ms, then returns a fixed pet result (Luna, with a vaccination certificate) if the query text contains pet( or allPets, and {"result": "SUCCESS"} otherwise. The response also carries made-up extensions such as a serving pod name. gql-introspect returns a fixed sample schema (Query, Mutation and Pet types) rather than running an introspection query. The endpoint, headers and variables are ignored.

What you can do

  • Read the sample schema in Schema Documentation.
  • Edit a query and click Execute Query (Ctrl+Enter) to see the sample response and its timing line.

There is nothing to configure and nothing is saved. For talking to a real GraphQL server today, use a tool such as curl or a dedicated GraphQL IDE; for REST calls see REST API Client.

electron packages/graphql-client

Source: packages/graphql-client.

Related guides

More in APIs, Contracts & Testing

Adapter Studio A prototype window that shows sample translations between Backstage, TypeSpec, Buf, Pact and Dev Container files and RobOS specs. Contract Studio A prototype console for browsing OpenAPI and AsyncAPI contracts and running Spectral, Pact and mock-server steps; the results are scripted samples. gRPC Microservice Client A BloomRPC-style window that lists sample protobuf services and shows canned responses; no RPC is sent. KGraph Parse Portal Crawls a folder into knowledge-graph nodes, classifies files by type, parses documents through Apache Tika when available, and indexes the result for search. REST API Client & Runner Request editor and collection runner wired to a sample Acme Petshop collection on a local Kubernetes cluster. It is a demo built around that one scenario, not a general REST client yet.