kit Changed params does not trigger load function

Changed params does not trigger load function

Open stephane-vanraes opened this issue 1 year ago • 4 comments

Describe the bug

Somehow it seems that changing params in nested routes does not trigger the load function to run again.

Reproduction

https://www.sveltelab.dev/md97yhs52ldziep

When first loading you will get get an empty object for params, navigating through the (very complex, highly usefull) application doesn't update this object. Refreshing when on a lower level will run the load again and show the correct.

Bizarelly enough (but likely a good pointer for where the bug happens) going down the tree (/home -> /aa -> /aa/bb) does not work while going "up" works as expected (/aa/bb -> /aa -> /home)

Logs

No response

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm

Severity

blocking an upgrade

Additional Information

No response

Jan 14 '24 12:01 stephane-vanraes

Explictly listening to one of the params in the load functions, like params.level_1 fixes this. So it seems the JSON.stringify in the page and the console.log are somehow not picked up.