When route component gets rendered?

[Dragomir-Ivanov]

Greetings,
Trying to wrap my mind around TSR, and against my use-case. I am using search params, and it seems that the whole route component is re-rendered when search param get changes. This is not intuitive and causes a lot of head scratching.

Given how these params are accessed via useSearch hook, wouldn't it more logical this hook to trigger the rerender of possibly only needed component, instead of the whole root component.

If the present behaviour is really intentional, is there any React recipe how to focus re-rendering only where it is needed, instead of the whole route component.

Thank you!

[TkDodo]

Can you show a minimal reproduction because afaik this shouldn't happen

[TkDodo]

everything is available on state, maybe not as easily explorable. getRenderedMatches(state) should give you matches, which will contain most of what you need.

[Dragomir-Ivanov]

Thank you @TkDodo. I dug through the sources, and found the function. This should work imperatively, and not reactive.
Will try asap, and comment/close the issue.

[Dragomir-Ivanov]

That's it then. It was getRenderedMatches(state) all I needed all along. I think this function needs more love in the Docs :)
I managed to optimize my rendering behavior for uncontrolled input elements.

Thanks @TkDodo. If I catch something else, surely I will report.

[TkDodo]

Please consider contributing to the docs :)

[Dragomir-Ivanov]

Will do in the coming days.