Merge branch 'master' of github.com:marmelab/react-admin into next

Author: Madeorsk

.github/workflows/deploy-doc-headless.yml

@@ -3,8 +3,9 @@ on:
     push:
         branches:
             - master
-            - next # TODO remove
-            - headless-doc-content # TODO remove
+
+    # Allows you to run this workflow manually from the Actions tab
+    workflow_dispatch:
 
 concurrency:
     group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}

.gitignore

@@ -14,6 +14,7 @@ examples/**/static
 examples/**/dist
 cypress/videos
 cypress/screenshots
+cypress/downloads
 /public
 /storybook-static
 .pnp.*

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 5.11.1
+
+* Fix `<Datagrid>` and `<DataTable>` bulk selection ([#10918](https://github.com/marmelab/react-admin/pull/10918)) ([djhi](https://github.com/djhi))
+* Revert usage on `<ListIterator>` in `ra-ui-materialui` ([#10919](https://github.com/marmelab/react-admin/pull/10919)) ([djhi](https://github.com/djhi))
+* [Doc] Update ra-realtime documentation for 5.2.0 ([#10914](https://github.com/marmelab/react-admin/pull/10914)) ([djhi](https://github.com/djhi))
+* [chore] Upgrade Cypress ([#10913](https://github.com/marmelab/react-admin/pull/10913)) ([djhi](https://github.com/djhi))
+
 ## 5.11.0
 
 * Add ability to use a `ReactNode` as create label in `<AutocompleteInput>` and `<SelectInput>` ([#10883](https://github.com/marmelab/react-admin/pull/10883)) ([Madeorsk](https://github.com/Madeorsk))

cypress/cypress.config.js

@@ -4,6 +4,7 @@ import vitePreprocessor from 'cypress-vite';
 export default defineConfig({
     fixturesFolder: 'fixtures',
     screenshotsFolder: 'screenshots',
+    downloadsFolder: 'downloads',
     videosFolder: 'videos',
     viewportWidth: 1280,
     viewportHeight: 720,

cypress/e2e/navigation.cy.js

@@ -12,7 +12,9 @@ describe('Navigation', () => {
             // additional rerenders, and otherwise it's the 'Skip to content' button that gets focused
             cy.contains('John Doe');
             cy.contains('Posts');
-            cy.get(ListPage.elements.profile).focus().tab();
+            cy.get(ListPage.elements.profile)
+                .focus()
+                .press(Cypress.Keyboard.Keys.TAB);
 
             cy.get(`${ListPage.elements.menuItems}:first-child`).should(
                 'have.class',
@@ -27,7 +29,7 @@ describe('Navigation', () => {
 
             ListPage.waitUntilVisible();
 
-            cy.get('body').tab();
+            cy.get('body').press(Cypress.Keyboard.Keys.TAB);
 
             cy.get(ListPage.elements.skipNavButton).should('exist');
         });

cypress/package.json

@@ -7,9 +7,8 @@
         "test": "yarn node ./start.js"
     },
     "devDependencies": {
-        "cypress": "^10.9.0",
-        "cypress-plugin-tab": "^1.0.5",
-        "cypress-vite": "^1.4.0",
+        "cypress": "^15.0.0",
+        "cypress-vite": "^1.7.0",
         "express": "^4.20.0"
     }
 }

cypress/support/index.js

@@ -1,5 +1,3 @@
-import 'cypress-plugin-tab';
-
 /*
  * This is a workaround for the ResizeObserver loop error that occurs in Cypress.
  * See https://github.com/cypress-io/cypress/issues/20341

docs/Architecture.md

@@ -219,7 +219,7 @@ Although this drawback exists, we accept it because the use of composition in re
 
 ## Hooks
 
-When you find that you cannot tweak a react-admin component using props, you can always turn to the lower-level API: hooks. In fact, the core of react-admin is a headless library called `ra-core`, which primarily consists of hooks. These hooks hide the framework's implementation details, allowing you to focus on your business logic. It's perfectly normal to use react-admin hooks in your own components if the default UI doesn't meet your specific requirements.
+When you find that you cannot tweak a react-admin component using props, you can always turn to the lower-level API: hooks. In fact, the core of react-admin is a headless library called [`ra-core`](https://marmelab.com/ra-core/), which primarily consists of hooks. These hooks hide the framework's implementation details, allowing you to focus on your business logic. It's perfectly normal to use react-admin hooks in your own components if the default UI doesn't meet your specific requirements.
 
 For example, the `<DeleteButton>` button used in `pessimistic` mode renders a confirmation dialog when clicked and then calls the `dataProvider.delete()` method for the current record. If you want the same feature but with a different UI, you can use the `useDeleteWithConfirmController` hook:
 

docs/Contributing.md

@@ -250,7 +250,7 @@ import { useListController } from 'ra-core';
 
 That's because the `react-admin` package simply re-exports components from internal packages. React-admin is a *distribution* of several packages, each dedicated to a specific feature. These packages can be found in [the `packages/` directory](https://github.com/marmelab/react-admin/tree/master/packages). Some of the more notable packages include:
 
-* `ra-core`: The core react-admin logic, without any UI.
+* [`ra-core`](https://marmelab.com/ra-core/): The core react-admin logic, without any UI.
 * `ra-ui-materialui`: The Material UI skin for react-admin.
 * `ra-data-*`: Data providers for various data backends.
 * `ra-language-*`: Interface translations for various languages.

docs/Features.md

@@ -279,13 +279,11 @@ And for mobile users, react-admin renders a different layout with larger margins
 
 React-admin components use Material UI components by default, which lets you scaffold a page in no time. As Material UI supports [theming](#theming), you can easily customize the look and feel of your app. But in some cases, this is not enough, and you need to use another UI library.
 
-You can change the UI library you use with react-admin to use [Ant Design](https://ant.design/), [Daisy UI](https://daisyui.com/), [Chakra UI](https://chakra-ui.com/), or even you own custom UI library. The **headless logic** behind react-admin components is agnostic of the UI library, and is exposed via `...Base` components and controller hooks.
-
-For instance, [`shadcn-admin-kit`](https://github.com/marmelab/shadcn-admin-kit) is a react-admin distribution that replaces Material UI with [Shadcn UI](https://ui.shadcn.com/).
+Fortunately, react-admin is built on top of a **headless library** called [`ra-core`](https://marmelab.com/ra-core/), which contains hooks and `...Base` components that you can use with any UI library. For instance, [`shadcn-admin-kit`](https://github.com/marmelab/shadcn-admin-kit) is a react-admin distribution that replaces Material UI with [Shadcn UI](https://ui.shadcn.com/).
 
 [![Shadcn admin kit](https://github.com/marmelab/shadcn-admin-kit/raw/main/public/shadcn-admin-kit.webp)](https://github.com/marmelab/shadcn-admin-kit)
 
-`shadcn-admin-kit` follows the same syntax conventions as react-admin, so most of the react-admin documentation still applies. For example, the `<ProductEdit>` component looks like this:
+`shadcn-admin-kit` follows the same syntax conventions as react-admin, so most of the react-admin syntax still applies. For example, the `<ProductEdit>` component looks like this:
 
 ```tsx
 import {
@@ -313,7 +311,7 @@ export const ProductEdit = () => (
 );
 ```
 
-Here is another example: a List view built with [Ant Design](https://ant.design/):
+You can also build apps with `ra-core` and [Ant Design](https://ant.design/), [Daisy UI](https://daisyui.com/), [Chakra UI](https://chakra-ui.com/), or even you own custom UI library. For example, here is a List view built with [Ant Design](https://ant.design/):
 
 ![List view built with Ant Design](./img/list_ant_design.png)
 
@@ -322,7 +320,7 @@ It leverages the `useListController` hook:
 {% raw %}
 
 ```jsx
-import { useListController } from 'react-admin'; 
+import { useListController } from 'ra-core'; 
 import { Card, Table, Button } from 'antd';
 import {
   CheckCircleOutlined,