Instead of a new function... Why we don't adapt the current one so, when an undefined or null timeout is passed, it does what's proposed in the issue?

Instead of a new function... Why we don't adapt the current one so, when an undefined or null timeout is passed, it does what's proposed in the issue?

Thank you for your suggestion! Considering that the semantics of refAutoRest are clearly tied to "Auto," directly modifying it might not be appropriate. Therefore, I have added a separate method. Additionally, we can use the refReset method and differentiate between automatic and manual modes through parameters. If you agree, I can further refine this solution.

Considering that the semantics of refAutoRest are clearly tied to "Auto," directly modifying it might not be appropriat

I totally agree with that. I'm actually surprised that there is function for auto option, but not manual one (refDefault is something different) :P In my opinion ideally there should be single function for both, where auto with timer would be just optional option. If not, refManualReset is still good option. But adding manual option for refAutoReset is really not intuitive.

When defaultValue is object, the reset function will not work.

try this example . click Update Ref btn then Reset Ref btn, the msg.value will not reset.

I’d personally like refManualReset to mirror refAutoReset as much as possible.

They can live as separate composables, but their API and internal structure should be very similar.

I’d personally like refManualReset to mirror refAutoReset as much as possible.

They can live as separate composables, but their API and internal structure should be very similar.

I have updated it. Kindly review.

I would really love this feature for reseting an ref back to its default value.

Open in StackBlitz

npm i https://pkg.pr.new/@vueuse/components@4644

npm i https://pkg.pr.new/@vueuse/core@4644

npm i https://pkg.pr.new/@vueuse/electron@4644

npm i https://pkg.pr.new/@vueuse/firebase@4644

npm i https://pkg.pr.new/@vueuse/integrations@4644

npm i https://pkg.pr.new/@vueuse/math@4644

npm i https://pkg.pr.new/@vueuse/metadata@4644

npm i https://pkg.pr.new/@vueuse/nuxt@4644

npm i https://pkg.pr.new/@vueuse/router@4644

npm i https://pkg.pr.new/@vueuse/rxjs@4644

npm i https://pkg.pr.new/@vueuse/shared@4644

commit: 5d64346

Hi @antfu 👋

I'm just following up on this PR which was recently approved. Whenever you have a moment, could you please take a look and consider merging it?

I'm really excited to contribute to VueUse and believe the function will be a handy

OK, I am good to have this new function if people found it useful

A deep ref option would have been nice, as it’s especially useful for forms or lists.