GraphQL Playground: Every developer's necessary instrument

GraphQL Playground is a powerful IDE (integrated development environment) dedicated to exploring, testing and debugging the GramQL API。 Playground makes full use of the GramQL compared to the traditional RET interface test tool The strong type systems and self-descriptive features provide an extremely fluid development experience.

Why do you need Playground online?

In the development process, we often need to quickly verify a search logic or not install a local client (e.g. Postman), or we need to be able to use a user-friendly approach. The Isomnia machine is debugging the production environment interface. This tool provides:

on-call: No software is required to be installed, and any public or trusted GraphQL nodes around the world are accessible by browsers.
Inner-source support: Through one key "Acquire" Schema, you can view all types, queries and changes in the service-end definition directly, which is equivalent to having a real-time update API document.
Local security: All Query History and Endpoint Configures are stored locally on your browser, and not uploaded to our server.
Performance analysis: Shows the response time and the size of the return package in real time, helping you to optimize the depth of the query and field selection.

The specific pains that are being solved.

Scenario one: Verify Cross-Drive (CORE) Problems.
CORS is often encountered when developing locally due to environmental differences Limit. Using online tools, it is quickly possible to judge whether the service-end configuration is a problem or the local development agent configuration.

Scenario 2: Complex variables debugged.
The GramQL variable system (Variables) requires strict JSON format. This tool provides independent variable editing windows and supports real-time formatting to ensure that parameters are passed on in a single way.

Scene three: Recover the history.
Have you written a very complex query and forgotten to save it? Our history record will automatically save the 20s you recently executed. bar, click and you can resume it.

GraphQL vs. REST: Core strengths

Accurate access to: RET often returns the entire resource object (over-fetching), while the GramQL Allows the front-end to specify the fields that are needed, which significantly saves bandwidth.
Single peer: No management /users , /posts , /comments Wait for dozens of ends, there's only one. /graphql End processes all requests.
Strong type of contract: Backend Schema, a document, with the front end automatically generating code by type (e. g. TypeScript) Defined) with a significant reduction in back-to-back and end-to-end connection costs.