State Exploration 4

/*

  Most liked approach because Maps are defined within the data structure for clarity, but details abstracted out.
  
  Example of only `some` of the various Maps needed for the tree. You can see how these can pile up quickly.

*/

var state = {

  // application data
  data: {},

  // I like declaring the Maps in the same space as the other data
  // but maybe not defining the function to reduce clutter.
  view: {

    // possibly inline because simple
    locationServicesOnline: ['data.locationServices', (Cerebral, state) => { state.locationServices.online }],
    locationServicesOffline: Map.locationServicesOffline,

    projectRunning: Map.projectRunning,
    projectTransitioning: Map.projectTransitioning,

    currentUserId: null,
    selectedUser: Map.selectedUser,
    sortedUsers: Map.sortedUsers,
    pendingUsers: Map.pendingUsers,

    selectedLocationId: null,
    selectedLocation: Map.selectedLocation,
    sortedLocations: Map.sortedLocations,
    disabledLocations: Map.disabledLocations

    locationSortType: 'ASC',
    locationSortBy: 'status',

    selectedConceptId: null,
    conceptSortType: 'DESC',
    conceptSortBy: 'name'
  }
}


// since you can't have functions on the tree, we can check for
// function definitiona and  convert the return value to Cerebral.Map automatically.
var Map = {

  locationServicesOffline() {
    return ['data.locationServices', (Cerebral, state) => { !state.locationServices.online }]
  }

  selectedUser() {
    return ['data.users', 'view.selectedUserId',
      (Cerebral, state) => {
        return state.users[state.selectedUserId]
      }]
  }
}