Applied review

Author: WiXSL

docs/Features.md

@@ -1096,7 +1096,7 @@ And last but not least, react-admin provides a **lock mechanism** to prevent two
 
 A user can lock a resource, either by voluntarily asking for a lock or by editing a resource. When a resource is locked, other users can't edit it. When the lock is released, other users can edit the resource again.
 
-```jsx
+```tsx
 export const NewMessageForm = () => {
     const [create, { isLoading: isCreating }] = useCreate();
     const record = useRecordContext();
@@ -1106,7 +1106,7 @@ export const NewMessageForm = () => {
     const isFormDisabled = lock && lock.identity !== identity?.id;
 
     const [doLock] = useLockOnCall({ resource: 'tickets' });
-    const handleSubmit = (values) => {
+    const handleSubmit = (values: any) => {
         /* ... */
     };
 

docs/Inputs.md

@@ -171,8 +171,8 @@ form state value --> format --> form input value (string)
 
 **Tip:** By default, react-admin inputs have the following `format` function, which turns any `null` or `undefined` value into an empty string. This is to avoid warnings about controlled/uncontrolled input components:
 
-```js
-const defaultFormat = (value) => value == null ? '' : value;
+```ts
+const defaultFormat = (value: any) => value == null ? '' : value;
 ```
 
 ## `fullWidth`

docs/PredictiveTextInput.md

@@ -338,7 +338,7 @@ If you rely on another API, you'll need to fetch it yourself.
 
 Finally, you don't need a completion API to use `<PredictiveTextInput>` in simple cases. For example, here is an implementation that deduces an email address from the first and last name directly in the browser:
 
-```jsx
+```tsx
 const getCompletionLocal = async ({ prompt = '' }) => {
     const { key, value, record } = getParamsFromPrompt(prompt);
     if (key === 'email') {
@@ -391,7 +391,7 @@ const getParamsForPrompt = (prompt) => {
         const [key, value] = line.split(':');
         acc[key] = value;
         return acc;
-    }, {});
+    }, {} as any);
     return { key, value, record };
 }
 ```

docs/Realtime.md

@@ -141,7 +141,7 @@ And last but not least, ra-realtime provides a **lock mechanism** to prevent two
 
 A user can lock a resource, either by voluntarily asking for a lock or by editing a resource. When a resource is locked, other users can't edit it. When the lock is released, other users can edit the resource again.
 
-```jsx
+```tsx
 export const NewMessageForm = () => {
     const [create, { isLoading: isCreating }] = useCreate();
     const record = useRecordContext();
@@ -151,7 +151,7 @@ export const NewMessageForm = () => {
     const isFormDisabled = lock && lock.identity !== identity?.id;
 
     const [doLock] = useLockOnCall({ resource: 'tickets' });
-    const handleSubmit = (values) => {
+    const handleSubmit = (values: any) => {
         /* ... */
     };
 

docs/Search.md

@@ -128,12 +128,12 @@ export const App = () => (
 
 If you're using [the `<ContainerLayout>` component](./ContainerLayout.md), you can use the `<Search>` component directly in the `toolbar` prop:
 
-```jsx
+```tsx
 // in src/MyLayout.jsx
 import { ContainerLayout } from "@react-admin/ra-navigation";
 import { Search } from "@react-admin/ra-search";
 
-const MyLayout = (props) => (
+const MyLayout = (props: any) => (
     <ContainerLayout {...props} maxWidth="xl" toolbar={<Search />} />
 );
 ```

docs/useSubscribeToRecord.md

@@ -20,7 +20,7 @@ The hook expects a callback function as its only argument, as it guesses the rec
 
 For instance, the following component displays a dialog when the record is updated by someone else:
 
-```jsx
+```tsx
 import { useState } from 'react';
 import { useEditContext, useFormContext } from 'react-admin';
 import {
@@ -48,7 +48,7 @@ const WarnWhenUpdatedBySomeoneElse = () => {
         formState: { isDirty },
     } = useFormContext();
 
-    useSubscribeToRecord((event) => {
+    useSubscribeToRecord((event: Event) => {
         if (event.type === 'edited') {
             if (isDirty) {
                 setOpen(true);
@@ -124,14 +124,14 @@ useSubscribeToRecord(event => { /* ... */ }, 'posts', 123);
 
 Whenever an event is published on the `resource/[resource]/[recordId]` topic, the function passed as the first argument will be called with the event as a parameter.
 
-```jsx
+```tsx
 const [open, setOpen] = useState(false);
 const [author, setAuthor] = useState<string | null>(null);
 const { refetch } = useEditContext();
 const {
     formState: { isDirty },
 } = useFormContext();
-useSubscribeToRecord((event) => {
+useSubscribeToRecord((event: Event) => {
     if (event.type === 'edited') {
         if (isDirty) {
             setOpen(true);
@@ -145,7 +145,7 @@ useSubscribeToRecord((event) => {
 
 **Tip**: Memoize the callback using `useCallback` to avoid unnecessary subscriptions/unsubscriptions.
 
-```jsx
+```tsx
 const [open, setOpen] = useState(false);
 const [author, setAuthor] = useState<string | null>(null);
 const { refetch } = useEditContext();
@@ -154,7 +154,7 @@ const {
 } = useFormContext();
 
 const handleEvent = useCallback(
-    (event) => {
+    (event: Event) => {
         if (event.type === 'edited') {
             if (isDirty) {
                 setOpen(true);
@@ -172,8 +172,8 @@ useSubscribeToRecord(handleEvent);
 
 Just like for `useSubscribe`, the callback function receives an `unsubscribe` callback as its second argument. You can call it to unsubscribe from the topic after receiving a specific event.
 
-```jsx
-useSubscribeToRecord((event, unsubscribe) => {
+```tsx
+useSubscribeToRecord((event: Event, unsubscribe) => {
     if (event.type === 'deleted') {
         // do something
         unsubscribe();