Merge branch 'master' into next

Author: djhi

docs/Admin.md

@@ -906,7 +906,7 @@ React-admin uses [React Query](https://tanstack.com/query/v5/) to fetch, cache a
   * The query is optionally configured with a refetch interval
 * Query results that are no longer used in the current page are labeled as "inactive" and remain in the cache in case they are used again at a later time.
 * By default, "inactive" queries are garbage collected after 5 minutes.
-* Queries that fail are silently retried 3 times, with exponential backoff delay before capturing and displaying an error to the UI.
+* Queries that fail are silently retried 3 times, with exponential backoff delay before capturing and displaying an error notification to the UI.
 * Query results by default are structurally shared to detect if data have actually changed and if not, the data reference remains unchanged to better help with value stabilization in regard to `useMemo` and `useCallback`. 
 
 If you want to override the react-query default query and mutation default options, or use a specific client or mutation cache, you can create your own `QueryClient` instance and pass it to the `<Admin queryClient>` prop:

docs/DataProviderWriting.md

@@ -440,6 +440,8 @@ export default {
 };
 ```
 
+**Note**: Throwing an `httpError` in your `dataProvider` will result in a notify popup appearing in your admin UI.
+
 ## Handling Authentication
 
 Your API probably requires some form of authentication (e.g. a token in the `Authorization` header). It's the responsibility of [the `authProvider`](./Authentication.md) to log the user in and obtain the authentication data. React-admin doesn't provide any particular way of communicating this authentication data to the Data Provider. Most of the time, storing the authentication data in the  `localStorage` is the best choice - and allows uses to open multiple tabs without having to log in again.

docs/DataProviders.md

@@ -68,7 +68,7 @@ React-admin uses [React Query](https://tanstack.com/query/v5/) to fetch, cache,
   * The query is optionally configured with a refetch interval
 * Query results that are no longer used in the current page are labeled as "inactive" and remain in the cache in case they are used again later.
 * By default, "inactive" queries are garbage collected after 5 minutes.
-* Queries that fail are silently retried 3 times, with exponential backoff delay before capturing and displaying an error to the UI.
+* Queries that fail are silently retried 3 times, with exponential backoff delay before capturing and displaying an error notification to the UI.
 * Query results by default are structurally shared to detect if data has actually changed, and if not, the data reference remains unchanged to better help with value stabilization in regard to `useMemo` and `useCallback`.
 
 If you want to override the react-query default query and mutation options, or use a specific client or mutation cache, you can create your own `QueryClient` instance and pass it to the `<Admin queryClient>` prop:

docs/DatagridAG.md

@@ -6,10 +6,12 @@ title: "FAQ"
 # FAQ
 
 - [Can I have custom identifiers/primary keys for my resources?](#can-i-have-custom-identifiersprimary-keys-for-my-resources)
-- [I get warning about unique key for child in array](#i-get-warning-about-unique-key-for-child-in-array)
+- [I get a warning about unique key for child in array](#i-get-a-warning-about-unique-key-for-child-in-array)
 - [How can I customize forms depending on its inputs values?](#how-can-i-customize-forms-depending-on-its-inputs-values)
 - [UI in production build is empty or broken](#ui-in-production-build-is-empty-or-broken)
 - [My Resource is defined but not displayed on the Menu](#my-resource-is-defined-but-not-displayed-on-the-menu)
+- [I get an error about control being null](#i-get-an-error-about-control-being-null)
+- [I get an error about a hook that may be used only in the context of a Router component](#i-get-an-error-about-a-hook-that-may-be-used-only-in-the-context-of-a-router-component)
 
 ## Can I have custom identifiers/primary keys for my resources?
 
@@ -118,7 +120,7 @@ const dataProvider = {
 };
 ```
 
-## I get warning about unique key for child in array
+## I get a warning about unique key for child in array
 
 When displaying a `Datagrid` component, you get the following warning:
 
@@ -167,3 +169,68 @@ export const MyMenu = () => (
     </Menu>
 );
 ```
+
+## I get an error about control being null
+
+In a view that contains a form, you may get the following error:
+
+> Cannot read properties of null (reading 'control')
+
+This is most probably because you have multiple versions of the `react-hook-form` package installed, one being a direct dependency in your project and the other brought by react-admin.
+
+First, you can run `npm list react-hook-form` to check if you have duplicate versions.
+
+To dedupe the package you can run `npm dedupe react-hook-form` or `yarn dedupe react-hook-form`.
+
+You may also edit the lockfile manually.
+
+Finally, you can use yarn’s [resolutions](https://yarnpkg.com/configuration/manifest#resolutions) or npm’s [overrides](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides) in your `package.json` file:
+
+```json
+{
+  "resolutions": {
+    "react-hook-form": "7.54.2"
+  }
+}
+```
+
+## I get an error about a hook that may be used only in the context of a Router component
+
+When using custom routing configurations, you may encounter strange error messages like:
+
+> `useLocation()` may be used only in the context of a `<Router>` component
+
+or
+
+> `useNavigate()` may be used only in the context of a `<Router>` component
+
+or 
+
+> `useRoutes()` may be used only in the context of a `<Router>` component
+
+or 
+
+> `useHref()` may be used only in the context of a `<Router>` component.
+
+or
+
+> `<Route>` may be used only in the context of a `<Router>` component
+
+These errors can happen if you added `react-router` and/or `react-router-dom` to your dependencies, and didn't use the same version as react-admin. In that case, your application has two versions of react-router, and the calls you add can't see the react-admin routing context.
+
+You can use the `npm list react-router` and `npm list react-router-dom` commands to check which versions are installed.
+
+If there are duplicates, you need to make sure to use only the same version as react-admin. You can deduplicate them using yarn's [resolutions](https://yarnpkg.com/configuration/manifest#resolutions) or npm’s [overrides](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides).
+
+```js
+// in packages.json
+{
+    // ...
+  "resolutions": {
+    "react-router-dom": "6.7.0",
+    "react-router": "6.7.0"
+  }
+}
+```
+
+This may also happen inside a [Remix](https://remix.run/) application. See [Setting up react-admin for Remix](./Remix.md#setting-up-react-admin-in-remix) for instructions to overcome that problem.

docs/FAQ.md

@@ -832,7 +832,7 @@ export const PostList = () => (
 
 ## `queryOptions`
 
-`<List>` accepts a `queryOptions` prop to pass [query options](DataProviders.html#react-query-options) to the react-query client. Check react-query's [`useQuery` documentation]([query options](https://tanstack.com/query/v5/docs/react/reference/useQuery)) for the list of available options.
+`<List>` accepts a `queryOptions` prop to pass [query options](DataProviders.html#react-query-options) to the react-query client. Check react-query's [`useQuery` documentation](https://tanstack.com/query/v5/docs/react/reference/useQuery) for the list of available options.
 
 This can be useful e.g. to pass [a custom `meta`](./Actions.md#meta-parameter) to the `dataProvider.getList()` call.
 

docs/List.md

@@ -71,7 +71,7 @@ export const useGetOne = <RecordType extends RaRecord = any, ErrorType = Error>(
         queryKey: [resource, 'getOne', { id: String(id), meta }],
         queryFn: queryParams =>
             id == null
-                ? new Promise(() => {})
+                ? Promise.reject('useGetOne: id cannot be null')
                 : dataProvider
                       .getOne<RecordType>(resource, {
                           id,

packages/ra-core/src/dataProvider/useGetOne.ts

@@ -74,7 +74,7 @@ ${children.map(child => `            ${child.getRepresentation()}`).join('\n')}
     referenceArray: {
         component: ReferenceArrayInput,
         representation: (props: ReferenceArrayInputProps) =>
-            `<ReferenceArrayInput source="${props.source}" reference="${props.reference}"><TextInput source="id" /></ReferenceArrayInput>`,
+            `<ReferenceArrayInput source="${props.source}" reference="${props.reference}" />`,
     },
     referenceArrayChild: {
         component: (