catstack

work in progress

modular framework for data-driven real-time apps

made by Enspiral Root Systems

inspired by ahdinosaur/mad-science-handbook

concepts

• modules
• streams
• services
• state, actions, effects, html views
• data logs and views
• commands

tools

• node
  • when in this directory run nvm use which will use the version of node specified in our .nvmrc.
• packages
  • install with npm install -g npm@3
  • to install a package, run npm install --save my-favorite-package

scripts

• create
• install
• start
• test
• lint
• format
• database

install

generate new project

catstack gen:project

start

dev

starts development environment

catstack start:dev

prod

starts production environment

catstack start

test

runs pull-test tests

can optionally take a glob

npm run test -- './todos/**/*.test.js'

default glob is ./**/*.test.js ignoring node_modules

lint

checks for standard style

can optionally take a glob

npm run lint -- './todos/**/*.js'

default glob is ./**/*.js ignoring node_modules

format

converts to standard style if possible

can optionally take a glob

npm run format -- './**/*.js'

default glob is ./**/*.js ignoring node_modules

db:clean

directory structure

• config/
  • config/index.js
  • config/${ NODE_ENV }.js
• ${ domain }/
• tests are any files that end in .test.js

domain overview

in contrast to frameworks like Rails which split our app into directories for each "type" of file (models, views, controllers), our app is split into directories for each conceptual domain, where each domain contains the various types of files within that domain.

each domain directory may contain any of:

• state.js: exports initial store state
• actions/*.js: exports store actions
• effects/*.js: exports effects
• getters.js: exports reselect getters
• pages/*.js: exports routed views
• elements/*.js: exports presentation views
• helpers/*.js: exports helper functions
• service.js: exports vas service

${ domain }/state.js

// cats/state.js`
module.exports = {
  create: () => ({
    state: {
      model: {},
      effect: null
    }
  })
}

/${ domain }/actions/*.js

// cats/actions/create.js
module.exports = {
  create: () => ({
    update: (model, action) => {
      console.log('cat:create', model, action)
      return model
    }
  })
}

/${ domain }/effects/*.js

// cats/effects/fetch.js
module.exports = {
  create: () => ({
    run: (effect) => {
      console.log('cat:fetch', effect)
    }
  })
}

/${ domain }/getters/*.js

// cats/getters/getCats.js
module.exports = {
  create: () => (state) => state.cats
}

/${ domain }/pages/*.js

// cats/pages/show.js
module.exports = {
  needs: {
    layout: 'first',
    cats: {
      profile: 'first'
    }
  },
  create: (api) => ({
    route: '/cats/:catId',
    view: api.layout((model) => api.cats.profile)
  })
}

/${ domain }/elements/*.js

// cats/elements/profile.js
module.exports = {
  needs: {
    html: 'first'
  },
  create: (api) => ({
    view: (cat) => api.html`
      <div>${cat.name}</div>
    `
  })
}

/${ domain }/service.js

// cats/service.js
module.exports = {
  needs: {
    data: 'first'
  },
  manifest: {
    all: 'source',
    get: 'async'
  },
  create: function (api) {
    const cats = [{
      name: 'Fluffy'
    }, {
      name: 'Zoe'
    }]

    return {
      methods: { all, get }
    }

    function all () {
      return pull.values(cats)
    }

    function get (id, cb) {
      cb(null, data[id])
    }
  }
})

FAQ

how do i do relations between models?

implement them in your getters.js file as selectors.

in the future, we should extract common relations into helper creators.