You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing routes, the shadow endpoint is not called when expected and even when it is called it does not receive URL searchParams. Only an initial, full page-refresh when on that URL works as expected.
Clicking the links changes the id param and / or the page url searchParam. The id param is picked up on the initial entry to a route, but the searchParam is null. Neither changes on subsequent clicks. A full page reload makes both be recognized and reflected in the page. Going back to home and then to the route makes the id param be picked up for that initial change (and page be null), but is then frozen again if navigating to a different id page.
Adding back the original load function to [id].svelte, even calling the new shadow endpoint, makes things work:
Describe the bug
When changing routes, the shadow endpoint is not called when expected and even when it is called it does not receive URL searchParams. Only an initial, full page-refresh when on that URL works as expected.
Reproduction
Using out-the-box new Svelte-Kit project.
__layout.svelte
(simply some links to click)index.svelte
(to allow changing to / from route)[id].svelte
(route to display data from endpoint)[id].ts
(endpoint just mirrors param / url.searchParams)Clicking the links changes the id param and / or the page url searchParam. The id param is picked up on the initial entry to a route, but the searchParam is null. Neither changes on subsequent clicks. A full page reload makes both be recognized and reflected in the page. Going back to home and then to the route makes the id param be picked up for that initial change (and page be null), but is then frozen again if navigating to a different id page.
Adding back the original load function to
[id].svelte
, even calling the new shadow endpoint, makes things work:Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: