Anthony Fu
Anthony Fu
Thanks for the awesome PR - sorry I didn't saw it until now
Thank you!
I am not very sure about this, ideally the `click` event should be a native event and a component should not emit it. Meanwhile, if the logic only exists in...
Maybe we could have an extra option to pass a handler, like `onMouseUp(duration: number, distance: number, isLongPress: boolean)` so users could pass custom logic to handle if they expect to...
I would love to have that for sure! But honestly just handling what we have right now is already beyond my capability. That would be awesome if you or anyone...
Yeah I think overriding makes sense as the `once` should be relevant to `whenever` rather than in the internal watch
Thanks for the PR - but I am honestly not very should if this should be in scope of VueUse - it seems you don't really need Vue reactivity in...
It could be better to add it Vue itself. Maybe someone could write a quick RFC for it? https://github.com/vuejs/rfcs
I am ok with having it, but I am concerned this can be potentially confusing. Can you help with: - Providing an explanation in the docs to clear the difference...
Oh now I see, you want a mutable computed ref, that updates when the source changes but that you can modify it freely from the outside right?