Sequence of promises

First of all, thanks for good work. I was struggling much when tried to set this library up for universal rendering (documentation requires little improvements 😅 and maybe I’ll help you with that later).

A little question:

module.exports = asyncConnect(
    [{
        key: 'products',
        promise: ({params, store: {dispatch, getState}}) => {
            return dispatch(fetchProducts())
                .then(data => {
                    const someValues = reduce(data.products, (values, product) => {
                        if (product.products.length) {
                            ...
                        }

                        return values;
                    }, []);

                    let size = 300,
                        filter,
                        value = find(someValues, v => v.label === 'String');

                    filter = `neededValues.id=in=(${value})`;

                    return dispatch(fetchSomeOtherData({
                        size,
                        filter
                    }));
                });
        }
    ],
    mapStateToProps, {
        ...
    }
)(Component);

Guess the picture is clear. I need to fetch data, after that fetch another data. Could you tell me please, is this code correct or may be there’s another, right way? And why params (which is route params?) are empty? 😞

[AVVS]

If you nest components then sequencing would be performed automatically, otherwise you solution is perfectly fine.

as for params - I believe it could be changed in the react-router, all the props are merely what’s been passed to a component from the router, so you might want to check the router object. I dont remember the exact structure from the memory, you can always console.log on the opts in the promise to see what you get 😃

[AVVS]

track promises manually, your nested dispatches should return some sort of promises or thunks or whatever, which you can keep track of in the asyncConnect. Otherwise it has no knowledge of whats happening inside and cant really tell whether you are done loading or not. Ideally anything that triggers an async action and needs to be resolved - must be connected somehow to the asyncConnect