children exports a function for plugging child components into a single, combined stream. It keeps the stream updated when components are added or removed using a MutationObserver, so if support for old environments is required, use a polyfill.

How to Use

Preparing the DOM

When setting up the HTML for a component, the top-level element should have a data-brk-container with a unique name.

<div data-brk-container="kid">{{text}}</div>

A helper is provided to make this easy to integrate with handlebars:

<div {{container "kid"}}>{{text}}</div>

This needs to be registered with the Handlebars runtime:

import { containerAttribute } from 'brookjs'
import Handlebars from 'handlebars/runtime';

Handlebars.registerHelper('container', containerAttribute);

The compiled templates will now provide the required container attribute through the helper.

Configuring the Stream

The children stream accepts a configuration object. The object’s keys should match the container attribute for the given component. The value can be either a component factory function:

import children from 'brookjs/children';
import kid from './kid';

export default children({ kid });

or a configuration object for that component, which defines the behavior of the child in relation to the parent:

import children from 'brookjs/children';
import { mapActionTo } from 'brookjs/helpers';

export default children({
    kid: {
        // only required value.
        // factory function for child taking el & props$
        factory: kid,
        // passed parents' `props$` stream & child key.
        // return value is passed to child onMount.
        // see below for key documentation.
        modifyChildProps: (props$, key) => props$.map(props => props.children[key]),
        // passed each child instance to modify child stream
        // return value is plugged into combined string (hence `preplug`)
        preplug: (kid$, key) => kid$.map(mapActionTo(CHILD_ACTION, PARENT_ACTION)).map(action => Object.assign({}, action, { meta: { key } }))

Handling Multiple Child Instances

If a single component will have multiple instances of a child component as a direct child, those instances must be differentiated. The data-brk-key attribute is used to distinguish them in the DOM, and the value of that attribute is passed to modifyChildProps along with the props$ stream. Here’s how it’s intended to be used.

First, an iterated child must have a data-brk-key attribute:

<div data-brk-container="child" data-brk-key="{{id}}">{{label}}</div>

A helper is also provided for the key attribute:

<div {{container "child"}} {{key id}}>{{label}}</div>

This also needs to be registered with the Handlebars runtime:

import { keyAttribute } from 'brookjs'
import Handlebars from 'handlebars/runtime';

Handlebars.registerHelper('key', keyAttribute);

The parent is then responsible for iterating over the props and rendering the children.

<div data-brk-container="parent">
    {{#each kids}}
        {{> kid}}

For each child, when it’s mounted or added to the DOM, modifyChildProps is called with the parent’s props$ stream and the value of the child’s key attribute. The returned stream should be of the child’s props. This is primarily useful to provide the correct props to the child’s onMount function.