[BUG] Ant Design Notifications message and description fields are swapped.

[sqwxl]

Describe the bug

The useNotificationProvider hook has swapped the description and message fields.

For example, a simple call like this:

import { useNotification } from "@refinedev/core";

//...

    const { open } = useNotification();

    useEffect(() => {
        open?.({
            type: "success",
            message: "Message",
            description: "Description"
        });
    });

Yields this notification:

Which is the opposite of the expected output, which should look like this:

As per the Ant Design Notification API, the message property corresponds to the notifications "title", whereas the description property is the "content". This is matches Refine's own specs for OpenNotificationParams.

This bug also affects indirect notification requests like the successNotification and errorNotification props of mutation parameters.

Steps To Reproduce

1. Create a vanilla Antd app and use the following for App.tsx

import { Refine, useNotification } from "@refinedev/core";
import { useNotificationProvider } from "@refinedev/antd";
import { App as AntdApp } from "antd";
import { useEffect } from "react";
import { BrowserRouter, Route, Routes } from "react-router-dom";

function App() {
	return (
		<BrowserRouter>
			<AntdApp>
				<Refine notificationProvider={useNotificationProvider}>
					<Routes>
						<Route index element={<Notif />} />
					</Routes>
				</Refine>
			</AntdApp>
		</BrowserRouter>
	);
}

export default App;

export const Notif = () => {
	const { open } = useNotification();

	useEffect(() =>
		open?.({
			type: "success",
			message: "This is the title",
			description: "This is the description",
		}),
	);

	return null;
};

2. Run npm run dev and open the page.
3. Each time the page is refreshed, a notification will be displayed with swapped elements:
   

Expected behavior

The props shouldn't be swapped.

Packages

• @refinedev/antd 5.44.0
• @refinedev/core 4.56.0

Additional Context

No response

[aress31]

The same issue affects the mui package - and most likely chakra and mantine too.

[alicanerdurmaz]

Hello @sqwxl, thanks for the issue.

We would love to fix this bug, but this change causes a breaking change and requires a major release. We don't want to bump the major version just for this bug. We will address this fix when we plan a major release for the UI packages.