`navigate` functions without `to` but with `search` causes a route error inside a layout route. about router

[SeanCassiere]

It has to do with this line.

For the fromPath it currently resolves to using the routeId of of the current route, which contains the layout identifier as a part of it.

It'll be matter of either sanitizing whats returned by the routeId or seeing if there's another property on the match that can be used here.

[SeanCassiere]

This has been fixed and released in 1.31.19.

[ruiaraujo012]

Thanks, I appreciated it.

[tatwater]

I'm on 1.31.28 and I'm still experiencing this same bug! Routes that have an id instead of a path are getting their id inserted into the URL when navigating with search params, which errors.

[SeanCassiere]

I'm on 1.31.28 and I'm still experiencing this same bug! Routes that have an id instead of a path are getting their id inserted into the URL when navigating with search params, which errors.

This has been fixed as of the 1.31.29 release.