directus-block

This library was generated with Nx.

Building

Run nx build directus-block to build the library.

Components

Dispatcher

Props

• config: Configuration the block dispatcher will use. This configuration will get merged with the base config of directus-block. In case of overrides, the passed configuration will always win over the directus-block configuration.
• blocks: Array of TBlockSerializerProps containing the actual blocks data. This is the prop that will be used by the block dispatcher to iterate through its children.
• block: In case you want to pass a single block
• children: Function receiving the current block TBlockSerializerProps as props. Will use BlockSerializer alone by default. This is useful in scenarios where you want every block to be wrapped in other components:

  <BlockDispatcher config={baseBlockDispatcherConfig} blocks={blocks}>
    {(block) => (
      <Container tokens={{ isLowestContainerLevel: true }}>
        <ErrorBoundary fallback={<ErrorFallback />}>
          <BlockSerializer {...block} />
        </ErrorBoundary>
      </Container>
    )}
  </BlockDispatcher>

This would allow to remove a lot of repetitive code accross blocks definitions, for example as they all need to be wrapped in a Container and an ErrorBoundary

Serializer

This component calls the good component in the configuration from the collection prop

Props

• item: The block's data. Can either contain just the block's id, be null (in that case, the id will need to be sent using the block's variables). If item only contains the id, it will be sent to the variables for making the query
• variables: The block's variables. Passing the id is necessary
• document: Can also be passed in the config. The document that will be used to make a query

Configuration

A configuration uses the components prop to map a key value, like so:

const config = {
  components: {
    block_wysiwyg: {
      default: (props) => <BlockWysiwyg {...props} />,
      document: BlockWysiwygDocument,
      defaultVariant: 'reversed',
      getVariant: (props) => props.settings.variants,
      variants: {
        reversed: (props) => (
          <ReversedThemeProvider>
            <BlockWysiwyg {...props} />
          </ReversedThemeProvider>
        )
      }
    }
  }
}

Props

• default: The default component if no variants/invalid variants are used
• defaultVariant: Overrides the default use of the default prop, instead mapping the default component on a specific variant
• getVariant: Callback to specify a different variant path from the one in the block's settings
• variants: key-value mapping of {[variant]: component}
• document: The necessary document for querying the data. This prop can either be passed directly to the block or in the config. Since Stack blocks don't yet have their own documents, you can override them and add their document like so:

import { blockWysiwygConfig } from '@okam/directus-block'

const brandConfig = {
  components: {
    block_wysiwyg: {
      document: BlockWysiwygDocument,
      ...blockWysiwygConfig.block_wysiwyg,
    },
    block_image: {
      default: (props) => <BrandBlockImage {...props} />
    },
  },
}

<BlockDispatcher config={brandConfig} />

Overriding the configuration with brand blocks

To override the base block dispatcher configuration, you name a block component configuration with the same key as the ones in the configuration.

For example, if this is the base configuration:

const baseConfig = {
  components: {
    block_wysiwyg: {
      default: (props) => <BlockWysiwyg {...props}>,
    },
    block_hero: {
      default: (props) => <BlockHero {...props}>,
    },
  },
}

But that you to call a branded wysiwyg component from the dispatcher configuration, you may pass the following configuration:

const brandConfig = {
  components: {
    block_wysiwyg: {
      default: (props) => <BrandBlockWysiwyg {...props} />
    },
    block_image: {
      default: (props) => <BrandBlockImage {...props} />
    },
  },
}

<BlockDispatcher config={brandConfig} />

In this example, the BlockWysiwyg definition would be overriden. However, you would now also have access to the block_image, and still retain access to the block_hero

You could also re-use only a part of the base configuration while overriding another part

import { blockWysiwygConfig } from '@okam/directus-block'

const brandConfig = {
  components: {
    block_wysiwyg: {
      default: (props) => <BrandBlockWysiwyg {...props} />,
      variants: blockWysiwygConfig.block_wysiwyg.variants,
    },
    block_image: {
      default: (props) => <BrandBlockImage {...props} />
    },
  },
}

<BlockDispatcher config={brandConfig} />

Extending the configuration with stack blocks

Some blocks may be in the Stack without being in the base configuration. To use them, simply import their own configuration from the stack and spread them in yours

import { blockHeroConfig } from '@okam/directus-block'

const brandConfigWithStackBlocks = {
  components: {
    block_image: {
      default: (props) => <BrandBlockImage {...props} />
    },
    ...blockHeroConfig,
  }
}