Schema

A schema defines the structure and content of an unbounded sequence of JSON values. Go to the schema concept page for an in-depth explanation.

This reference contains every schema that rngo provides out-of-the-box. You can use them in your simulation as-is, or combine them to create custom schemas.

Every schema is part of a namespace, and should be referenced using the fully-qualfied name, e.g json.object. However some schemas may be referenced without the namespace, e.g. object.

core

Primitives used to build other, higher-level schemas.

• core.constant
• core.function
• core.reference
• core.select

json

The rngo schemas are a superset of JSON Schema, meaning that JSON Schema can be used to define a simulation.

These schema types correspond to a JSON Schema type and expect the same fields as their JSON Schema equivalent (or a subset thereof during the rngo beta)

• json.object
• json.array
• json.string
• json.integer
• json.number
• json.boolean
• json.null
• json.enum
• json.const

id

Different types of identifiers.

• id.integer
• id.uuid

time

Deterministic time values.

• time.now
• time.offset

person

Data associated with humans.

• person.name
• person.givenName
• person.familyName

internet

Internet and network-related data.

• internet.email

phone

Phone number generation.

• phone.number

address

Physical address generation.

• address.address1
• address.address2
• address.postalCode
• address.state

content

Placeholder and sample content generation.

• content.lorem

util

Utility schemas for common use cases.

• util.nullable
• util.set