Roman

Guys, I'm working on my own library inspired by this great project. It works on Vue 3. But I used new Composition API and some hooks. I want to provide...

I'm not sure if this is possible. The problem is in the storage listeners, as it is written in the [MDN docs](https://developer.mozilla.org/en-US/docs/Web/API/Window/storage_event), they will not work on the same page,...

@nolde don't be upset. Vueuse already has a solution for you. Just use [createGlobalState](https://vueuse.org/shared/createGlobalState/). Like this ``` // store.js import { createGlobalState, useStorage } from '@vueuse/core' export const useGlobalState =...

https://github.com/vueuse/vueuse/issues/1595

Actually, it can be useful, if you have one mutator that doesn't trigger the hooks. For example, if you need to save raw data from a backend.

Hi, @Nks! Thank you for raising this important issue! I thought it was intuitively understood that when you 'create dialog', you create it with its props( I think it's better...

Ok, an alternative solution with backward compatibility. You can set `keepClean` options in `createConfirmDialog`, so it will solve this bug, but it will not break old code: ``` const propsBehaviorOptions...

@Nks Fix is on the way: [props-fix](https://github.com/harmyderoman/vuejs-confirm-dialog/tree/props-fix)! You can fix your issue by using it like that: ``` const dialog = createConfirmDialog(Modal, { message: 'initial message' }, { chore: true,...

Fixed by https://github.com/harmyderoman/vuejs-confirm-dialog/pull/22

It's a known problem. It occurs when you have default values for your props. Sorry, it will be fixed somewhen in the future