Describe what's incorrect/missing in the documentation
In v6, what's in window.location and what is rendered happend to be quite in sync. So, if your react component parsed window.location to get the URLSearchParams, that worked quite fine. In v7, though, window.location (and the URL shown in the browser) will change first, whiles there is still the old route being rendered and re-rendering. There should be some mention and guidance in the v7 migration guide about that.
In our case that led to various exceptions related to variables/props being null in the page that was still open, because it's mandatory query parameters were suddenly missing - the URL in window.location was already that of ne navigation target, not API-compatible with the old page rerendering. While this might not have been good development practice in v6, and it might not have been supported behaviour, a little hint in the upgrade guide would have saved us quite some time.
Describe what's incorrect/missing in the documentation
In v6, what's in window.location and what is rendered happend to be quite in sync. So, if your react component parsed window.location to get the URLSearchParams, that worked quite fine. In v7, though, window.location (and the URL shown in the browser) will change first, whiles there is still the old route being rendered and re-rendering. There should be some mention and guidance in the v7 migration guide about that.
In our case that led to various exceptions related to variables/props being null in the page that was still open, because it's mandatory query parameters were suddenly missing - the URL in window.location was already that of ne navigation target, not API-compatible with the old page rerendering. While this might not have been good development practice in v6, and it might not have been supported behaviour, a little hint in the upgrade guide would have saved us quite some time.