Socket
Socket
Sign inDemoInstall

@sanity/schema

Package Overview
Dependencies
41
Maintainers
48
Versions
1248
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @sanity/schema

## Terminology


Version published
Weekly downloads
125K
decreased by-8.45%
Maintainers
48
Created
Weekly downloads
 

Readme

Source

Sanity schema

Terminology

  • Schema A collection of types
  • Type A specification of a data structure. Available through schema lookup.
  • Member type A member type is a type contained by a schema type. For example, an array may specify the allowed item types by defining members types from schema types. A reference may be a reference to a set of other types. A member type is not added to the schema and is not available through schema lookup, but rather exists as a property of the owner type.

Constraints

No inheritance

You are almost always better off using composition, rather than inheritance hierarchies

E.g.:

const PERSON = {
  type: 'object',
  name: 'person',
  fields: [
    {name: 'firstName', type: 'string'},
    {
      name: 'address',
      type: 'object',
      fields: [
        {
          name: 'street',
          type: 'string',
        },
      ],
    },
  ],
}

If one were to introduce a user type, it would be tempting to think of it as a subtype of person, adding a few additional fields specific for the user type, like this:

const USER = {
  // modelling user as a subtype of person
  name: 'user',
  type: 'person',
  fields: [
    {
      name: 'username',
      type: 'string',
    },
  ],
}

A problem with the above is: how do we merge the fields? Should the fields from PERSON be placed before the fields from USER? What if both types define the same field, should the subtype override? What if that field is an object where we'd like to keep some of the fields, but remove others? It quite quickly becomes messy.

A better solution would be to define common fields outside, and re-use them across types:

e.g.:

const FIRST_NAME_FIELD = {name: 'firstName', type: 'string'}
const ADDRESS_FIELD = {
  name: 'address',
  type: 'object',
  fields: [
    {
      name: 'zip',
      type: 'string',
    },
    {
      name: 'street',
      type: 'string',
    },
    {
      name: 'city',
      type: 'string',
    },
  ],
}

const PERSON = {
  type: 'object',
  name: 'person',
  fields: [FIRST_NAME_FIELD, ADDRESS_FIELD],
}

const USER = {
  type: 'object',
  name: 'person',
  fields: [FIRST_NAME_FIELD, {name: 'username', type: 'string'}, ADDRESS_FIELD],
}

You could even take this further by extracting the individual fields of the address type and compose in different ways.

Keywords

FAQs

Last updated on 23 Apr 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc