4.0.0-rc.0 - infinite re-render in list component when useResolvedPath is used

Adding const resolved = useResolvedPath('') cases the following issues:

• List component causes infinite re-render.
• web page URL is automatically updated to include URL parameters (when loading a page by link https://vw0pg1.sse.codesandbox.io/#/posts, the browser redirects to https://vw0pg1.sse.codesandbox.io/#/posts?displayedFilters=%7B%7D&filter=%7B%7D&order=ASC&page=1&perPage=10&sort=id)

What you were expecting: useResolvedPath usage in list component should not impact react-admin behavior:

• when I enter https://vw0pg1.sse.codesandbox.io/#/posts to blank page in browser, it should stay in https://vw0pg1.sse.codesandbox.io/#/posts without adding parameters
• the page should not go into infinite re-render loop

What happened instead:

Steps to reproduce:

Related code:

https://codesandbox.io/s/winter-sky-vw0pg1?file=/src/posts/PostList.tsx:707-1355

Notice how console.log keeps printing messages, and also render count keeps updating.

If I comment out lines that cause issues, then react-admin starts behaving properly

export const PostList = (props: any): JSX.Element | null => {
  const ref = React.useRef(1);
  ref.current = ref.current + 1;

  const basename = useBasename();
  const resolvedPath = useResolvedPath(""); // THIS LINE CAUSES ISSUES
  console.log({ basename, resolvedPath });  // THIS LINE CAUSES ISSUES

  const filters = [
    <TextInput
      key="1"
      label="id"
      source="id"
      alwaysOn
      sx={{ width: "100%", minWidth: "350px" }}
    />
  ];

  return (
    <Fragment>
      <div>{ref.current}</div>
      <List {...props} filters={filters}>
        <Datagrid rowClick="edit">
          <TextField source="id" label="ID" />
        </Datagrid>
      </List>
    </Fragment>
  );
};

Other information:

Environment

• React-admin version: 4.0.0-rc.0
• Last version that did not exhibit the issue (if applicable):
• React version:
• Browser:
• Stack trace (in case of a JS error):

[panfiva]

I noticed that if I add disableSyncWithLocation to my list, then I no longer have this issue. I suspect that the issue is caused by navigate call inside useListParams.ts; it seems it is trying to navigate to on each re-render, triggering another re-render.

[fzaninotto]

Fixed by #7457