AES Encrypt & Decrypt
Encrypt text with a password using AES-GCM, and decrypt it back.
Draft a GraphQL type definition from a sample JSON response.
Only fields present in every sampled record are marked non-null — relaxing a non-null later is a breaking change for clients.
The JSON to GraphQL Schema converter drafts SDL type definitions from a sample response: a type per nested object, list types for arrays, non-null markers on fields that are always present, and the ID scalar for identifier fields.
Wrapping a REST endpoint in GraphQL starts with writing types that mirror the response, and that first draft is mechanical. Paste the JSON and get SDL: a type per nested object, list types for arrays, and the built-in scalars mapped from the values.
Fields present in every record are marked non-null with an exclamation mark; the rest are nullable, which is the GraphQL default and the safer choice for anything coming from an upstream service. Keys named id, _id or uuid are typed as the ID scalar rather than String, since that is what clients expect for cache keys. You can also emit input types instead, for the mutation arguments that mirror the same shape.
Keys named id, _id or uuid are typed as ID, which is what clients such as Apollo use as the normalised cache key.
Only fields present in every sampled record are marked non-null, because relaxing a non-null later is a breaking change for clients.
Emit output types for queries, or input types for the mutation arguments that mirror the same shape.
Each nested object becomes its own named type rather than being inlined, which is the only form SDL allows.
Arrays become [Type!] with the inner non-null marker where it belongs, which is the part hand-written SDL usually gets wrong.
One representative payload from the endpoint you are wrapping.
Nested types take their names from the keys that hold them.
Output types for queries, input types for mutation arguments.
Paste the SDL into your schema file and wire up the resolvers.
No, only the type definitions. Resolvers are where your actual business logic lives, and no generator can infer that from a payload.
As String, because GraphQL has no built-in date scalar. Most schemas define a custom DateTime scalar — swap the type once you have declared it.
A field present in every sampled record is marked non-null. Be cautious with that: non-null is a permanent contract, and relaxing it later is a breaking change for clients.
It marks a field as a unique identifier. It serialises as a string but tells clients such as Apollo which field to use as the cache key, which matters for normalised caching.
What people who use the JSON to GraphQL Schema think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON to GraphQL Schema. It takes half a minute and no account.
Write the first reviewEncrypt text with a password using AES-GCM, and decrypt it back.
Generate TypeScript interfaces from a sample JSON payload.
Convert between JSON arrays and NDJSON, one compact document per line.
Reformat a MAC address between every notation, and decode what it means.
Your browser, engine, platform, languages and what it supports.
Generate ULIDs — sortable by creation time and case-insensitive.
Check YAML parses and find the line where the indentation goes wrong.
Convert a date into every ISO 8601 form, including week and ordinal dates.