Add lifecycle callbacks (beforeDelete, afterUpdate, etc.) to facilitate dataProvider customization

[fzaninotto]

Problem

Developers must put their data handling / domain logic in the dataProvider, but that isn't very practical. The dataProvider quickly becomes a mess of if(resource ==='...') that is hard to read and to maintain.

Solution

Allow developers to decorate an existing dataProvider with lifecycle callbacks.

const dataProvider = withLifecycleCallbacks(baseDataProvider, [
    {
        resource: 'posts',
        beforeDelete: async ({ id }) => {
            // delete related comments
            const { data: comments } = await baseDataProvider.getList(
                'comments',
                {
                    filter: { post_id: id },
                    pagination: { page: 1, perPage: 100 },
                    sort: { field: 'id', order: 'DESC' },
                }
            );
            await baseDataProvider.deleteMany('comments', {
                ids: comments.map(comment => comment.id),
            });
            return { id };
        },
    },
]);

• Add code
• Add unit tests
• Use in simple example
• Add e2e test
• Add documentation

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
react-admin	🔄 Building (Inspect)		Dec 19, 2022 at 1:58PM (UTC)
react-admin-storybook	🔄 Building (Inspect)		Dec 19, 2022 at 1:58PM (UTC)

[fzaninotto]

Switching to RFR

[slax57]

Great testing though 💪

[fzaninotto]

Review applied