Generalising effects/actions/data about easy-peasy

[adrienWeiss]

I've been using a function that takes the name and the url to fetch (that would be the function to call for you, getAllMaterialien or getAllFormen) that returns the state tree

{
  [name]: {
    list: [],
    loadAll: effect(...) => {
      ...
      dispatch.helper[name].setList(...
  },
}

and then spreading those

const model = {
  ...materialState,
  ...formState,
},

But I agree with you, one would want to easily parse the local state, but it is also important to be able to dispatch elsewhere.
Also, with the project growing there is a risk of conflicting names.

[ctrlplusb]

@RuedigerLudwig I have opened a PR which may help you with this. Utilising the meta data exposed to the effect function you could do something like:

const list = (endpoint) => ({  
  list: [],
  ids: select(state => R.pluck('id', state.list)),
  loaded: select(state => state.list === []),
  setList: (state, payload) => ({ ...state, list: payload }),
  loadAll: effect(async (dispatch, _payload, _getState, _injections, meta) => {
    const data = await endpoint()
    const setList = R.path(meta.parent.join('setList'), dispatch);
    setList(data);
  }),
})

And then use it like so:

const store = {
  helper: {
    material: {
	  other: '👋',
      ...list(getAllMaterialien)
    },
    form: {
      ...list(getAllFormen)
    },
  },
}

Let me know what you think. 😊

@adrienWeiss - would appreciate your input too.

[ctrlplusb]

The only thing I dislike about this helper approach is that it can be harder to visualise your state tree, however, when the typescript work lands you should get typesafe autocomplete on your model which will help dramatically. :)

[ctrlplusb]

Available in latest release.

https://github.com/ctrlplusb/easy-peasy/releases/tag/v1.7.0

🤘

[RuedigerLudwig]

Wow, that is quick. Thank you for the quick addition. I am pretty sure that it solves my use case.