pinia-plugin-persistedstate VS sortablejs

If you use a standard Pinia store, you can use plug-ins. For example, you can use pinia-plugin-persistedstate to let the user start each new session where they left off. Or you can use pinia-orm to simplify handling large amounts of tabular data.

How about this plugin, then?: https://github.com/prazdevs/pinia-plugin-persistedstate.

When your application starts, fill your Pinia/Vuex store with data from the user's previous session. This is done automatically by pinia-plugin-persistedstate or the Vuex equivalent.

pinia-plugin-persistedstate: keeps your Pinia store synced with the user's browser localStorage. In other words, if your user closes their browser and then returns to your Vue app later, they will have the same state as when they left.

You also mentioned that the positions should be stored in localStorage. I would store the positions in Pinia, and then add the pinia-plugin-persistedstate plug-in. It's one import statement and one line of code to add that plugin, and then your Pinia state is automatically persisted in localStorage. It beats having to write and troubleshoot the storage logic yourself.

I've used the pinia-plugin-persistedstate package and has worked fine for me.

I have a Vue 3 / TypeScript app that uses a combination of Firebase, Pinia, Vue Concurrency, and the Pinia Persisted State Plugin.

We've been using SortableJS for years for similar functionality.

https://sortablejs.github.io/Sortable/

Well, it worked. But only for one case: dragging stuff within only one column. You see, stimulus-sortable uses SortableJS under the hood, which is powerful.

Maybe: https://github.com/SortableJS/Sortable Can do this not sure.

Well, there are obvious leading contenders like `https://sortablejs.github.io/Sortable/` and, within the `vue` space, `https://sortablejs.github.io/vue.draggable.next/`. Most of the stuff I looked at was unmaintained (lots not updated for vue3).

I really disliked the vuedraggable was handling nesting, and it's just a wrapper around a sortable. At the end of the day, my problem was simple enough that I didn't want a 500kb dependency. If you're wanting to do something like the OP but with nesting, I'd definitely start by looking at Sortable, though (maybe wrapping it the way you want).

Have you looked into alternatives to SortableJS btw? It's a good library but it's also pretty big (43kb) based on https://github.com/SortableJS/Sortable/blob/master/Sortable.min.js.

after(() => { cy.task('sendMail', 'This will be output to email address')       .then(result => console.log(result));   }) //zadanie A it("navstiv stranku a vyhladaj a elementy v casti Framework Support", ()=>{ cy.visit('https://sortablejs.github.io/Sortable/#cloning')

Check out https://sortablejs.github.io/Sortable/