[future] How to do Redux store (if we do it again)

[rufuspollock]

Various "notes to self" about we do Redux store if we do it again (from mid Feb)

Our app state (redux store):

{
  # maybe only one data package - but what about publisher page ...
  # theDataPackage: {},
  packages: {
    #  id looks like "publisher/name"
    "{id}": datapackageDescriptor - normalized ...
  },
  resources: {
    "{dataPackageId}::{idx}
  },
  views: {
    "{dpId}::{viewIndex}"
  }
  dataPackageResourcesByName: # do we need this ...
  # data package resource data - maybe we should name that way ...
  blobs: {
    "{resourceId}": ...
  }
}

Note:

• We need a unique id for every object.

FAQ

 How to handle nested entities like DataPackages?

• Ans: normalize your data
• See http://redux.js.org/docs/basics/Reducers.html#note-on-relationships
  • See: https://github.com/reactjs/redux/issues/994
• Use: https://github.com/paularmstrong/normalizr

http://redux.js.org/docs/recipes/reducers/NormalizingStateShape.html http://redux.js.org/docs/recipes/reducers/UpdatingNormalizedData.html

Asynchronous Data

http://redux.js.org/docs/advanced/AsyncActions.html

https://github.com/reactjs/redux/issues/99 - Best async loading technique (old issue)

Various options:

• thunk - don't really understand it yet
• https://github.com/redux-saga/redux-saga

Structure for actions - use https://github.com/acdlite/flux-standard-action

{
  type: 'ADD_TODO',
  payload: 'xxx'
  error: true
}

[rufuspollock]

INVALID. Not an issue and now very obsolete.