Making a DDAU checkbox list in Ember.js

Nico Mihalich

Engineering Manager

Nico Mihalich

Data Down, Actions Up (A refresher)

An important part of creating stable, maintainable Ember applications is following the Data Down, Actions Up (DDAU) paradigm. This means that your data comes in at the route level and is displayed further down in your UI (by templates and components), while when you want to manipulate that data, you trigger an action which gets sent back up to the route that manipulate the data at its source. This makes your application simple and easy to reason about because there is a single source of truth for your data and the route that manipulates the data.

Okay… so?

So, it’s hockey season! Let’s finally build that favorite player voting app you’ve always wanted. We’ll display a list of players via a list of checkboxes and have the user select which ones they like. Our input will be a list of strings, and we want the output to be another list of strings. Following DDAU, ideally we want our checkboxes to not actually manipulate a selected value directly, but send an action back up which manipulates our model and marks the player as selected. (We’ll leverage One Way Controls for that).


Model: Our model hook is dead simple:

model() {
  return [];

Also we’ll need some options to select from. Let’s put that in the controller:

import Ember from 'ember';

const { Controller, set } = Ember;

export default Controller.extend({
  init() {
    set(this, 'playerOptions', [
      'Phil Kessel',
      'Sidney Crosby',
      'Tyler Seguin',
      'Steven Stamkos',
      'Connor McDavid',
      'Patrick Kane'

And a simple template:

  <h2>Pick your favorites</h2>
    {{#each playerOptions as |player|}}
        {{!TODO Checkbox}}

  <h2>You picked</h2>
    {{#each model as |player|}}


Now we have some options, and a place to select them into. Let’s write the checkbox logic! The API for a checkbox looks something like:

{{one-way-checkbox selected update=(action "someAction")}}

Where selected is a boolean.

For our use case, the checkbox should be selected when the player is in the model. Note our input and output are both lists of strings, no selected attribute. So how do we mark it as selected if we don’t store it?

Quick detour into helpers!

We want to have selected in our template be true when an item is in an array. We can write a helper that does this for us which we can use in the template to return our selected boolean value:

import Ember from 'ember';

const { Helper: { helper } } = Ember;

export function includes([haystack, needle]) {
  return haystack.includes(needle);

export default helper(includes);

This enables us to write

{{one-way-checkbox (includes model player) ...}}

It’s also useful in that if your model returns some options, the template is reactive to that and automatically marks them as selected because the helper is computing it from the higher up data flowing into it.



So far so good, but if we click on the checkbox… it doesn’t do anything. We’ll need an update action, which we want in our route (using ember-route-action-helper).

  actions: {
    togglePlayer(player, checked) {
      let model = get(this, 'currentModel');
      if (checked) {
      } else {


Now we can insert a checkbox using our includes helper and action.

  {{one-way-checkbox (includes model player)
    update=(route-action "togglePlayer" player)}}

And we’re done! Here’s a demo.

I hope this demonstrates a practical example of DDAU in Ember to build a pretty common UI element.


Stay in the Know

Get the latest news and insights on Elixir, Phoenix, machine learning, product strategy, and more—delivered straight to your inbox.

Narwin holding a press release sheet while opening the DockYard brand kit box