pass ownProps to areStatesEqual

[z-vr]

We have a use case when we need to use areStatesEqual and access ownProps at the same time. This PR solves the problem.

function compareStates(paths = [], a, b) {
    return paths.filter((path) => {
        const valueA = get(a, path);
        const valueB = get(b, path);
        return valueA !== valueB;
    });
}

const mapStateToProps = ({
    data: {
        campaign,
    },
}, { data: { id } }) => {
    const campaigns = getEntities(campaign, 'client_id', id);
    return {
        campaigns,
    };
};

export default connect(mapStateToProps, null, null, {
    areStatesEqual(prevState, nextState, { id }) {
        const paths = ['data.campaign.by.client_id.${id}.ids'];
        const differentPaths = compareStates(paths, prevState, nextState);
        const areEqual = differentPaths.length === 0;
        if (!areEqual) {
            console.log('[!] %s are not equal', differentPaths.join());
        }
        return areEqual;
    },
})(Client);

[timdorr]

This was already discussed in #781

[z-vr]

@timdorr it doesn't make any sense to me why you would not allow to access own properties in this method. The use case is exactly the same as the author you linked, and you're forcing me to run mapStateToProp which I do want to avoid. If your users are asking for it why is it so difficult? What's the argument against it?

You said

I would work to make that easier to query by doing some of the work upfront in your reducer.

But it's already easy for me to query, I just don't even want to query when irrelevant slices change. Is this too big of an ask?