Remount component on parameter change

Consider the following route definition:

'/users/:id': UserView

Navigating from /users/1 to /users/2 will not remount the example UserView component and therefore any actions (eg. fetching the targeted user) binded to onMount are not triggered.

This seems to be intended (probably #L476) but what it is the reason behind that? Is it possible to add an optional config to force it?

---

ps. I’ve just checked other common js routers - it seems that they follow similar approach, but in my opinion having to “watch” the router parameters adds unnecessary boilerplate and overall it’s not the same as remounting/reinstantiating.

[ItalyPaleAle]

It is done on purpose indeed, for the best user and developer experience 😃

What you can do is to watch for changes to params.id and reactively update your component.

You can see an example here: https://github.com/ItalyPaleAle/book-app-demo/blob/master/src/components/Book.svelte

[vkurko]

@ItalyPaleAle, thanks for the answer. But you shouldn’t break existing behavior! What I (and others) ask for is simply the ability to switch existing behavior to “remount” the component. This setting can be turned off by default, so this change will not affect anyone. But users who need this “remount” can enable it in their projects.

Thanks