Read a schema

Loading…

All tools › Requests and interfaces

Read a schema

Types and fields listed, and which type is named by which — the question a schema is opened for.

It runs entirely in this browser tab: the code you paste is never uploaded, and nothing here is executed, built or fetched — it is read and something else is written. Open your browser's network panel and try it.

What it takes

A GraphQL schema document.

An example

type Query {
  orders(first: Int): [Order!]!
  customer(id: ID!): Customer
}

type Order {
  id: ID!
  total: Float!
  customer: Customer!
}

type Customer {
  id: ID!
  name: String!
  email: String
}

Settings

Show
Choices: Fields, Types, What names what.
Filter
Only what contains this word.

How to use it

  1. Paste your text into the box above, or open a file.
  2. Adjust the settings beside it until the result is what you wanted.
  3. Copy the result, or save it as a file. The result updates as you type.

Questions

Is my code uploaded anywhere?
No. The whole application is carried as WebAssembly and runs on your own device. That matters here as much as anywhere: a curl command pasted out of a terminal has a live token in it, a stack trace has your customers' identifiers in it, and a configuration file has a password in the middle of a connection address.
Does anything here run what I paste?
Never. The command explainer explains and does not execute; the Dockerfile reader reads and does not build; the request builder writes a command and does not send it. Each tool says so on its own result, and each says what that costs it — a linter that did not build the image cannot tell you the image builds.
Will an escape survive a round trip?
Yes, and there is a test that says so: every language's escaper has its unescaper beside it, and an awkward string with quotation marks, backslashes, tabs, a null and an emoji in it goes through both for every language on every run of the test suite.
Why does it refuse a pattern instead of matching nothing?
Because matching nothing looks like an answer. The glob matcher reads a stated subset — the stars, the question mark, character classes, brace lists and a leading negation — and a pattern using anything else comes back named rather than quietly matching none of your files.

Other tools for requests and interfaces

curl to code
A command as the same request in six languages, with the token masked by default.

Build a request
Method, headers and body as a command, a request file or a table of its parts.

WHERE clause
Rules as a clause with the values kept outside it, which is the only safe way to write one.

Sample answer
A shape of fields as a JSON answer, repeatable from a seed and never mistaken for data.

Format a query
A query indented or minified, with its variables named and its braces counted.

All forty tools