@data-fair/lib-common-types

The JSON schemas and TypeScript types shared across the data-fair stack (session state, accounts, events, notifications, themes, catalog and processing plugin contracts…), with their generated validators and a few helpers built on top of them. Services, Vue applications and plugins import it so that they all speak the same contracts.

Install

npm i @data-fair/lib-common-types

Optional peer dependency: tinycolor2 (v1), only needed by theme/index.js.

Modules

Each directory module exports its generated types (and validate / assertValid / returnValid when listed) from index.js, and its raw JSON schema as the default export of schema.js.

Usage

Session

The session state is usually obtained through the session middleware of @data-fair/lib-express or useSession of @data-fair/lib-vue; this package provides its type and the checks. See the data-fair-session skill.

import { type SessionState, assertAccountRole } from '@data-fair/lib-common-types/session/index.js'

// throws httpError(401) if not authenticated, httpError(403) if the active account does not have the role
assertAccountRole(sessionState, resource.owner, 'admin')

getAccountRole(sessionState, account, { allAccounts?, acceptDepAsRoot? }) returns the role instead of throwing ('admin' in admin mode and for the user's own account, null if none).

Referencing the shared schemas

Schemas built with @data-fair/lib-types-builder can $ref the shared schemas by their $id (https://github.com/data-fair/lib/<name>):

owner: { $ref: 'https://github.com/data-fair/lib/account' },
topic: { $ref: 'https://github.com/data-fair/lib/event#/$defs/topicRef' }

Plugins

import type { PrepareFunction, RunFunction, ProcessingContext } from '@data-fair/lib-common-types/processings.js'
import type { CatalogPlugin } from '@data-fair/lib-common-types/catalog/index.js'

See the data-fair-processing skill.

Scopes

A service declares its scope families once; the matching of session/index.js (hasScope, exact or bare umbrella, never prefix) stays the same.

import { defineScopes, oauth2SecurityScheme, oauth2Alternatives } from '@data-fair/lib-common-types/scopes.js'

const scopes = defineScopes({
  notifications: {
    tiers: ['read', 'write'],
    descriptions: {
      umbrella: { fr: 'Tous les droits sur les notifications', en: 'All notification scopes' },
      read: { fr: 'Lire ses notifications', en: 'Read own notifications' },
      write: { fr: 'Gérer ses abonnements', en: 'Manage own subscriptions' }
    }
  }
})

// notifications:write notifications all:write all:admin
requireScope(scopes.acceptedScopes('notifications', 'write'))

// the oauth2 scheme of the service's OpenAPI document
oauth2SecurityScheme(scopes, { directoryUrl, locale: 'fr' })

// an operation's security: [{ sdCookie: [] }, { oauth2: ['notifications:write'] }, { oauth2: ['notifications'] }, ...]
const security = [{ sdCookie: [] }, ...oauth2Alternatives(scopes.acceptedScopes('notifications', 'write'))]

• acceptedScopes(family, tier): the family's declared tiers at or above tier, the umbrella, then all:<tier> and the higher global tier scopes. A tier the family does not declare throws.
• familyScopes(family): every scope that reaches some tier of the family, for a coarse gate.
• scopeDescriptions(locale): the description of every declared scope, the all:* ones included.
• oauth2Alternatives(accepted): one OpenAPI security alternative per accepted scope. A single { oauth2: [a, b] } would mean a token needs both. What an all:* scope grants is read from the operations that list it, data-fair's platform document relies on this form.
• The global tier scopes and their descriptions are owned here (globalScopes), identical in every service. all is reserved as a family name.