Vue.js

We'll why do you want this? If you want (in this context) "invisible" data shared with different components use a store or a composable. If you want parameters in your url that have an effect on the content that is displayed, use the router params. Mixing both requirements would let to 1. User enters URL with name and ID 2. A piece of code rewrites the url, memorizes the name and removes that info from the url. That's a SEO nightmare.

I guess the problem is a perspective problem: that's no pollution, that's a clear description of what the user will see. Also the user could copy the url, send it to a colleague and this colleague would see a different page if you want to "cleanup" the url.

You can use the .push() method of vueRouter to push a state.

It is quite handy and, imo, better than the store solution:

• if you want to just pass some data to another page, for example to pre-populate a form, you would create a store just as a middle-man instead of a way to store relevant data (for example, fetched data)
• the push + state solution persist on page refresh, until you push a new state to the page or the user empty the cache, so depending on the use case it is preferable to the store

Anyhow, it would look like this: button @click="router.push({name: 'settings', state: { ...myObj } })">Go to page

to access it: route.history.state

There is no need to stringify the object, so it's quite handy. https://developer.mozilla.org/en-US/docs/Web/API/History https://router.vuejs.org/guide/essentials/navigation.html#History-Manipulation

The code isn't visible for some reason on lemmy. I'm not sure if it'll be in this comment. Okay it wasn't. Removing brackets to see if it works now.

router-link :to=name "url", params:id:1 router-link