React-router: [v6] setParams from useSearchParams ignores current location

[d3dc]

Version

6.0.0-alpha.5

Test Case

https://codesandbox.io/s/react-router-1w91e

Steps to reproduce

call setParams() in a Container with an outlet.

Expected Behavior

search params are appended to the current path

Actual Behavior

search params replace the current path.

I assume this is because "*" doesn't actually pop any route segments - I'm struggling to find v5 docs that warn about this however.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
You can add the fresh label to prevent me from taking any action.

[vjpr]

I am seeing this issue too. Pretty sure it is a bug...

Related to how navigate doesn't work on dynamic routes like foo/*.

[clarkbynum]

@mjackson @ryanflorence can we reopen this issue?

EDIT: seeing this issue on v6.0.0-beta.0

[kombuchafox]

I'm also seeing this unfortunately

[kombuchafox]

So the work around is just doing

const location = useLocation();
...
navigate({
      pathname: location.pathname,
      search: "?" + createSearchParams({ ...newParams }),
    });

The issue is that useSearchParams tries to navigate to the parent path (?) which breaks children paths
https://github.com/ReactTraining/react-router/blob/dev/packages/react-router-dom/index.tsx#L418