01_normalReducer.js

import { createReducer } from 'src/utils';

const LOAD_POST = 'LOAD_POST';
const LOAD_POST_SUCCESS = 'LOAD_POST_SUCCESS';
const LOAD_POST_FAIL = 'LOAD_POST_FAIL';

const initialState = {
  $isLoading: false,
  $didFailLoading: false,
  post: null,
};


// action creators, exports etc etc etc, you get the point. this is in our case generated by an internal 
// yeoman generator by running `yo generate reducer post` or some such.
// this works, but if we streamline things we either have to write a codemod or manually refactor
// all the generated bits.

02_macroReducer.js

import reducer from 'reducer.macro';

reducer('post')

// doing it this way could result in the same code, but if we change the underlying macro
// we wouldn't need to write said codemods or refactor individual reducers....
// we'd obviously have to put some more thought into api flexibility / escape hatches,
// but that's a trade-off I can see leaning towards macro's in some of our use-cases.