v3 - $params when reset route not take [param] about routify

[jakobrosenberg]

Hi @foxkdev

This is by design. When you reset, you clear everything before the reset and the reset component becomes the root component. Since the respective component [channel] doesn't exist after the reset, it won't provide the parameter to the route.

It's possible that we can create a solution for this, but it has to work with

• render
• load
• parameters

For instance, if you have a site that's protected by the load function, you might want to reset (disable) the root load at /tenants and at /tenants/[id]/ you want to reset the view, but in both case you want to access the parameters from the entire URL.

Currently the route fragments (components) before the reset component are simply removed before the route is processed. This doesn't allow for much flexibility, but we could instead tag the fragments like this:

// pseudo route fragment
{
  node: RNode,
  params: {},
  shouldLoad: true, // new prop
  shouldRender: true, // new prop
  shouldProvideParams: true // new prop
}

I can't tell if this is straight forward yet, but I'll have a look.

[foxkdev]

I think for better usage when im reset is becase I want reset module(layout), not params.

for example i have this routes:

- [channel]/profile.svelte
- [channel]/iframe.svelte
- _module.svelte
- _module-full.svelte

view /[channel]/profile use module but [channel]/iframe i want use module-full, so in this view im reset, but im need access to params.

I think this is normal usage, I suggest:

have meta param reset to reset all(module and params) and create new param "module"(by default 'module') to assign module custom but with rest of params.

[jakobrosenberg]

🎉 This issue has been resolved in version 3.0.0-next.157 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀